On Wed, August 30, 2006 9:18 am, Craig Dibble wrote: > Voytek Eymont wrote:
thanks, Craig > Er, no - c should just toggle the command column on or off to show the > full command line. If it doesn't work for you then 'h' should show you the OK, I see, yes, I wasn't looking at the right area; the culprit is 'syslogd' (which I already noticed was a little 'loaded') > available options. Failing that, just try something like this: > ps wax -o cmd |grep [p]erl this is even more precise: pop-b4-smtp > > And you should get a listing of all perl processes running (there are > numerous different ways you can call that ps command to get the same > result, before anyone points it out, just pick your favourite if you have > one). > > At a guess I'd say you're running apache_modperl and something's running > amok. yes, it seems popb4smtp was running amok >>> it's a good idea to see if you can find out why it's happening in the >>> first place if you can, as in all likelihood it will recur. >> >> yes, I would like to find that out as it was, when trying to restart >> apache, I ended up in a loop where it failed to start up again, and, >> under the circumstances, I ended up restarting the system (as I couldn't >> recall how to clear the problem...) > > If you haven't cleared all the processes it won't restart. Try > 'apachectl stop' first, (or apache2ctl), if that doesn't work, try > 'killall apache' (or httpd, depending on your system), and if that > doesn't work try: I was using service httpd restart and service httpd stop/start I'll use your suggestion and try apachectl next time I need to > > ps wax |grep [a]pache > > and do a kill -9 on the PIDs, which is the brute force way of clearing > it. and, if it still fails, I;ll try the above many thanks for all the clues'n'tips ! now, why is popb4 running amok.... -- Voytek -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
