** NOTE to SuSE-UK Memebers -- This is a forwarded e-mail from a
discussion between Mark and myself which is clarifying a slight mishap on
my part. Sorry :) **
--- MJ Ray
On 2003-06-19 12:37:37 +0100 Thomas Adam
wrote: Oppps, errm, no. You're quite right. Kmail is not a daeman and so will not have an active .pid file. My mistake -- I guess that coffee hadn't kicked in at that point :)
It's OK, I was just making sure that my coffee had kicked in ;-) Maybe you'd like to correct it on the list. I don't know if KMail writes a pid file somewhere under $HOME.
No, the only time a process would write a PID file is if it is a daeman. This is to ensure that the process scheduler doesn't kill it or try and assign it to the same number (should another process start). It also acts as a lock file, and can be used in instance such as... kill -9 $(cat /var/run/pid/pid.pid) Furthermore, it would be somewhat of a bad idea to start writing .pid files in $HOME, since almost all daemans run under a dummy user such as "Nobody" or in most cases "Root". Writing them to $HOME posses as security risk. but we're digressing... :) So, what I am saying is that you should ignore the bit about "rm /var/run/pid/kmaik.pid" as it never has, nor will it ever exist. HTH, -- Thomas Adam ===== Thomas Adam "The Linux Weekend Mechanic" -- www.linuxgazette.com ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/