Re: DirectConnect 5.3 and Eclipse
Re: DirectConnect 5.3 and Eclipse
- Subject: Re: DirectConnect 5.3 and Eclipse
- From: LD <email@hidden>
- Date: Thu, 9 Jun 2005 10:47:38 +1000
Hi there,
On 09/06/2005, at 3:49 AM, Hunter Hillegas wrote:
By using launchd and the scripts from OS X Server, I was able to
get my machine to TRY to start wotaskd...
But, it dies when it starts:
Jun 8 10:42:41 aibook launchd: com.webobjects.wotaskd: exited with
exit code: 1
Jun 8 10:42:41 aibook launchd: com.webobjects.wotaskd: 9 more
failures without living at least 60 seconds will cause job removal
Any ideas why this would be the case?
What's the plist file look like (i.e., text dump). This usually
occurs when the arguments are wrong for the launchd.plist OR the app
being started is not following the guidelines for daemons...
From man launchd.plist:
Daemons or agents managed by launchd are expected to behave certain
ways.
A daemon or agent launched by launchd MUST NOT do the following
in the
process directly launched by launchd:
o fork(2) and have the parent process exit(3) or _exit(2).
o Call daemon(3)
A daemon or agent launched by launchd SHOULD NOT do the
following as a
part of their startup initialization:
o Setup the user ID or group ID.
o Setup the working directory.
o chroot(2)
o setsid(2)
o Close "stray" file descriptors.
o Change stdio(3) to /dev/null.
o Setup resource limits with setrusage(2).
o Setup priority with setpriority(2).
o Ignore the SIGTERM signal.
A daemon or agent launched by launchd SHOULD:
o Launch on demand given criteria specified in the XML
property
list. More information can be found in launch(3).
o Catch the SIGTERM signal.
with regards,
--
LD
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden