On Tuesday 22 August 2006 08:42, paul kölle wrote: > works from command prompt: > gentoo ~ # start-stop-daemon -v --start --chuid helma --background > --pidfile /var/run/helma-default.pid --make-pidfile --startas > /opt/sun-jdk-1.5.0.08/bin/java -- -Djava.headless=True -Xmx64m -Xms64m > -jar /opt/helma-1.5.1/launcher.jar -h /opt/helma-1.5.1/ -w 8080 > > -> app is running > > > gentoo ~ # /etc/init.d/helma start > * Starting checkconfig with instance default > * This is passed to java: -Djava.headless=True -Xms64m -Xmx64m -jar > /opt/helma-1.5.1/launcher.jar -h /opt/helma-1.5.1/ -w 8080 > * Starting helma instance default. ... > Starting /opt/sun-jdk-1.5.0.08/bin/java... > Detatching to start /opt/sun-jdk-1.5.0.08/bin/java...done. > [ ok ] > > -> app not running > > I'm mostly interested in changing the user at startup and pid file > handling. If start-stop-daemon won't work I'd need to add sudo to > RDEPEND and grab the PID from "ps U" or similar... I'd prefer doing it > in a more "standard" way though.
What is /opt/sun-jdk-1.5.0.08/bin/java ? Does it change it's process name at all? Maybe you need to use the --name option. I ask as for init scripts we have a bash wrapper around s-s-d that is a lot more strict than s-s-d itself. For example it should only be used for daemons - ie what you call is expected to be a daemon. Thus it is useless for shell scripts that call daemons. See the courier-imap fiasco for details on this. For hints on what we do, checkout /lib/rcscripts/sh/rc-daemon.sh Thanks -- Roy Marples <[EMAIL PROTECTED]> Gentoo/Linux Developer (baselayout, networking) -- [email protected] mailing list
