| 1 |
Roy Marples wrote: |
| 2 |
> On Tuesday 22 August 2006 08:42, paul kölle wrote: |
| 3 |
[ snipp ] |
| 4 |
>> Starting /opt/sun-jdk-1.5.0.08/bin/java... |
| 5 |
>> Detatching to start /opt/sun-jdk-1.5.0.08/bin/java...done. |
| 6 |
>> [ ok ] |
| 7 |
>> |
| 8 |
>> -> app not running |
| 9 |
>> |
| 10 |
>> I'm mostly interested in changing the user at startup and pid file |
| 11 |
>> handling. If start-stop-daemon won't work I'd need to add sudo to |
| 12 |
>> RDEPEND and grab the PID from "ps U" or similar... I'd prefer doing it |
| 13 |
>> in a more "standard" way though. |
| 14 |
> |
| 15 |
> What is /opt/sun-jdk-1.5.0.08/bin/java ? Does it change it's process name at |
| 16 |
> all? Maybe you need to use the --name option. |
| 17 |
Hmm, I think it is the java "interpreter" and it doesn't seem to change |
| 18 |
its name. "cat /proc/<pid>/stat shows "java" as the process name, so |
| 19 |
--name would be the same for all running java apps. |
| 20 |
|
| 21 |
[...poking around..] |
| 22 |
Ok, fixed ;) Apparently s-s-d doesn't like linebreaks (not even escaped) |
| 23 |
between "--startas $command", and "-- $args". |
| 24 |
|
| 25 |
> |
| 26 |
> I ask as for init scripts we have a bash wrapper around s-s-d that is a lot |
| 27 |
> more strict than s-s-d itself. For example it should only be used for |
| 28 |
> daemons - ie what you call is expected to be a daemon. Thus it is useless for |
| 29 |
> shell scripts that call daemons. See the courier-imap fiasco for details on |
| 30 |
> this. |
| 31 |
I'm pretty sure I do not understand the details here ;) I just thought |
| 32 |
about s-s-d as something you can use as a wrapper for backgrounding and |
| 33 |
pid stuff... |
| 34 |
|
| 35 |
thanks again, |
| 36 |
Paul |
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-dev@g.o mailing list |
Archives