Roy Marples wrote: > On Tuesday 22 August 2006 08:42, paul kölle wrote: [ snipp ] >> 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. Hmm, I think it is the java "interpreter" and it doesn't seem to change its name. "cat /proc/<pid>/stat shows "java" as the process name, so --name would be the same for all running java apps.
[...poking around..] Ok, fixed ;) Apparently s-s-d doesn't like linebreaks (not even escaped) between "--startas $command", and "-- $args". > > 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. I'm pretty sure I do not understand the details here ;) I just thought about s-s-d as something you can use as a wrapper for backgrounding and pid stuff... thanks again, Paul -- [email protected] mailing list
