Hi John, On 16 Jul 2014, at 3:16 AM, John Pollard <j...@pollardweb.com> wrote:
> My solution was to use Upstart config files in /etc/init and ditch the older > SysVinit config file in /etc/init.d > Where there was one file to start wotaskd and javamonitor, I now have one for > each > Using this approach, wotaskd is now restarting automatically if I kill it. > For the record, my Upstart config came out like this: Are you still using this approach? I spent some time this afternoon trying to get this working with Upstart on Amazon Linux (where 0.6.5 is still the default version of Upstart), but didn’t get very far. I started just with wotaskd, and although I could get it to launch on boot, I couldn’t: * Manually stop wotaskd with “sudo stop wotaskd”—this would just hang. * Get Upstart to respawn wotaskd if I killed the process manually. Is there any chance you could go into your setup here with more detail? -- Paul Hoadley http://logicsquad.net/
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to arch...@mail-archive.com
