On 2010-07-08 01:09, Hans-Christoph Steiner wrote: > > I guess there should be a third inlet for the signals? I see something > like this: > > STDIN signals process name > | | | > | | | > [process /usr/sbin/httpd] > | | | > | | | > STDOUT STDERR status messages, like PID, current process name, > state, etc.
hmm, iirc "process name" is there mainly to override the process given as the argument. sending a new "process name" (e.g. "/usr/sbin/apache2") into the last inlet surely won't start the new process, would it? for me starting a new process seems to be a very "hot" action. then i don't see a reason why we need different inlets for "process name" and "signals", as both are there to control the the current/future process from "outside". so i would basically simplify this to the attached interface. as for sending signals: even though i like signals very much, there is no such concept on w32 (or at least it is not readily available for the little programmer). personally i would hate to have the 5th object for the same task that is still highly platform dependent.
#N canvas 277 80 961 366 10; #X msg 70 32 run /usr/sbin/apache2; #X obj 135 233 print STDOUT; #X obj 200 207 print STDERR; #X msg 200 151 1 2 3; #X text 253 149 <- STDIN; #X obj 70 333 route PID status; #X text 83 311 process information; #X text 235 33 start a new process (stop/detach the old one first) ; #X msg 89 64 signal 9; #X text 157 63 send signal 9 (KILL) to the process; #X obj 70 184 process /usr/bin/sh; #X text 383 108 the 1st inlet is reserved for meta-controlling the process (starting \, stopping \, suspending \, ...); #X text 390 218 the 1st outlet is reserved for meta-information from the process (PID \, status \, ...); #X text 389 161 the other inlets are reserved for communication TO the process (there's only one more inlet that is connected to the process's STDIN); #X text 392 260 the other outlets are reserved for communication FROM the process (there's an outlet connected to the process's STDOUT and an outlet connected to the process's STDERR); #X connect 0 0 10 0; #X connect 3 0 10 1; #X connect 8 0 10 0; #X connect 10 0 5 0; #X connect 10 1 1 0; #X connect 10 2 2 0;
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
