Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

shockme (2685)

shockme
  reversethis-{gro.dnuowtixe} {ta} {kcohs}
http://exitwound.org/
AOL IM: stephenhargrove (Add Buddy, Send Message)

If you really must have more information about me, see my home node [perlmonks.org] at PerlMonks [perlmonks.org] or my journal [exitwound.org] at exitwound.org.

Journal of shockme (2685)

Tuesday September 03, 2002
09:53 AM

Evolution Solution

[ #7495 ]
Background: Quitting Evolution is no guarantee. I knew that, but didn't think much of it. Even though you File->Exit or X out of Evolution, there is a real possibility that the processes won't be killed.

I've been bitten by this before, and I got bit again over the long weekend. Evolution was still running on my machine at the office, grabbing all of my email.

So, I wrote a little script using Proc::ProcessTable to kill it and crontab'd the script. So now, every night at 5:30, Evolution will die.

NB: For some reason, I couldn't get Proc::Killfam to do it's job. I followed the docs to the letter, but no joy. So, I had to shove a system("kill -9 $p->{pid}") into the script. Works like a hose.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.