Re: PHP_ProcessWatcher

In general this sounds interesting to me. But how about handling the "events" inside PHP? I mean, being able to call a function and not <execute> a separate program? And how about resetting the script-timeout in your php-script-loop? I'm not against the package - parsing output of a process-"watching"- tool seems a good idea. But maybe you could include advanced features in your tool - or separate some some core-functionality (e.g. parsing of a ps-output etc.) in a separate package? If I wish to count all httpd-processes using your lib, dump a list of all httpd-pids or simply want to show a "ps ax"-like output that is generated by a PHP-script from an array into which you parsed the ps- output that would be quite handy from my view. So in my oppinion the class should contain a bit more general functionality. Stefan On 7 Nov 2003 at 11:28, Michael Wallner wrote: > Hi folks, > > this is rather "collecting thoughts and optinions" than a proposal. > > However, I've read a comment in a mag about ps-watcher[1], and I liked > the idea, so it came to me writing PHP_ProcessWatcher... :-) > > This package is at an very early development stage, but seems to work > already. It is based on an XML config file and checks running > processes by psing (I know - it runs only on non-Win32). > > If you're interested or even annoyed, make some (though I would > appreciate *many* ;-) comments or check it out: > > http://dev.iworks.at/PEAR/proposals/PHP_ProcessWatcher.html > http://dev.iworks.at/PEAR/PHP_ProcessWatcher-0.1.tgz > > Have fun :-) > > [1] http://ps-watcher.sourceforge.net/ > > Regards, > -- > Michael - < mike(@)php.net > > >