2249 ? S 0:00 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2250 ? S 0:00 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2251 ? S 0:27 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2252 ? S 0:00 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2253 ? S 0:00 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2254 ? S 0:00 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2255 ? S 0:00 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2257 ? S 0:00 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2258 ? S 0:28 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2259 ? S 0:13 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2260 ? S 0:07 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r 2261 ? S 0:01 ./vdr -w 60 -l 3 -p 2001 -s /usr/local/bin/vdrshutdown -r
I'd rather like to see each plugin show their names and parameters in ps, like heartbeat does.
Am Dienstag, 12. April 2005 22:34 schrieb Harald Milz:
[...]
I'd rather like to see each plugin show their names and parameters in ps, like heartbeat does.
Well these are not processes but threads, which all belong to the main VDR app... I guess there is no "easy" way to distinguish which plugin a thread belongs to...
Greetings, Sascha
Sascha Volkenandt wrote:
Am Dienstag, 12. April 2005 22:34 schrieb Harald Milz:
[...]
I'd rather like to see each plugin show their names and parameters in ps, like heartbeat does.
Well these are not processes but threads, which all belong to the main VDR app... I guess there is no "easy" way to distinguish which plugin a thread belongs to...
Greetings, Sascha
Well, each thread can be given a "description", so if somebody finds a way to make the 'ps' list show a given string for a particular thread, it should be possible to show something more informative here.
Klaus
-----Original Message----- From: vdr-bounces@linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf Of Klaus Schmidinger
[snip]
Well, each thread can be given a "description", so if somebody finds a way to make the 'ps' list show a given string for a particular thread, it should be possible to show something more informative here.
Yeah, it would be nice - but the linux kernel is missing support for setproctitle(), and the only user-space implementations I can find use the incredibly hacky method of overwriting the characters in the argv[] array.
An example implementation: http://cvs.linux-ha.org/viewcvs/viewcvs.cgi/linux-ha/heartbeat/setproctitle. c?rev=1.10.2.1&content-type=text/vnd.viewcvs-markup.
Chris
On 4/13/05, Chris Warren dvb@ixalon.net wrote:
-----Original Message----- From: vdr-bounces@linuxtv.org [mailto:vdr-bounces@linuxtv.org] On Behalf Of Klaus Schmidinger
[snip]
Well, each thread can be given a "description", so if somebody finds a way to make the 'ps' list show a given string for a particular thread, it should be possible to show something more informative here.
Yeah, it would be nice - but the linux kernel is missing support for setproctitle(), and the only user-space implementations I can find use the incredibly hacky method of overwriting the characters in the argv[] array.
An example implementation: http://cvs.linux-ha.org/viewcvs/viewcvs.cgi/linux-ha/heartbeat/setproctitle. c?rev=1.10.2.1&content-type=text/vnd.viewcvs-markup.
Chris
This seems to be the way to do it. See [1] and [2].
There are other tools that uses this method e.g. readproctitle in Dan Bernstein's deamontools e.g. [3]
Bye Ulrich
[1] http://lkml.org/lkml/2004/8/18/34 [2] http://lkml.org/lkml/2004/8/20/208 [3] http://web.mit.edu/afs/sipb/service/qmail/src/admin/daemontools-0.76/compile...
-
Chris Warren -
Harald Milz -
Klaus Schmidinger -
Sascha Volkenandt -
Ulrich Petri