Hello Tom,
First of all sorry for the late answer.
I've added a ticket on our forge not to forget.
http://forge.fusioninventory.org/issues/548
Can you come, if it's possible for you, on our IRC channel to discuss
this issue ? (#fusioninventory on irc.freenode.net).
Thanks a lot for this message, and we really need to check what should
be the right way to do.
Walid.
On 22/12/2010 16:23, Tom Carpenter wrote:
I downloaded and installed the prebuilt fusioninventory-agent 2.1.7
for OS X
http://prebuilt.fusioninventory.org/stable/macosx-intel/fusioninventory-agent_macosx-intel_2.1.7-2.pkg.tar.gz
"agent.cfg" provided in that package uses the following defaults
daemon=1
AND
daemon-no-fork=0
Looking at the text of Daemon.pm (Proc::Daemon) it appears as though the
settings in "agent.cfg" would cause fusioninventory-agent to fork.
When run
with the default settings (above) in "agent.cfg" it looks like
fusioninventory-agent
may violate launchd's restrictions (launchd.plist(5))
http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man5/launchd.plist.5.html#//apple_ref/doc/man/5/launchd.plist
A daemon or agent launched by launchd MUST NOT do the following in the
process directly launched by
launchd:
• Call daemon(3).
• Do the moral equivalent of daemon(3) by calling fork(2) and have the
parent process exit(3)
or _exit(2).
Perhaps it doesn't matter if it does, I'm just trying to develop a better
understanding of fusioninventory-agent and launchd before deploying
the agent.
- Tom Carpenter
_______________________________________________
Fusioninventory-user mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/fusioninventory-user
_______________________________________________
Fusioninventory-user mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/fusioninventory-user
