Jeff,
Just as a note for the future, you can get by setting up a cronjob by using
watch
watch "ps aux | grep check.cgi | awk '{print $2}' | xargs kill"
would find and kill every pid linked to check.cgi. By default watch runs
every 5 seconds, but you can change that with -n. You can either append &
on it to have it run in the background or use screen so that it will
continue to run even if you disconnect.
On Tue, Nov 25, 2008 at 4:32 PM, Jeff Lasman <[email protected]> wrote:
> On Tuesday 25 November 2008 01:18 pm, David Kaiser wrote:
>
> > Well, it is possible that some process was able to change it's
> > process info to read "/usr/bin/perl -w./check.cgi" when there was no
> > check.cgi file anywhere. Just a decoy trick from a bad process.
>
> Perhaps ...
>
> My additional post with more information never made it to the list.
> Let's see if this one does. Maybe I'm ending up on blocklists used by
> this list <frown>...
>
> In the meantime I was rounding a per-minute cronjob to kill check.cgi
> each time it found it ... now I've turned that off and will see if any
> show up again so i can check as you suggested.
>
> Jeff
> --
> Jeff Lasman, Nobaloney Internet Services
> P.O. Box 52200, Riverside, CA 92517
> Our jplists address used on lists is for list email only
> voice: +1 951 643-5345, or see:
> "http://www.nobaloney.net/contactus.html";
> _______________________________________________
> LinuxUsers mailing list
> [email protected]
> http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
>
--
Peter Manis
(678) 269-7979
