jari(_dot_)aalto(_at_)poboxes(_dot_)com writes:
I have a deadlock on in my .procmailrc and I don't know what to
do. Thank god I have verbose and backups on all the time so I won't
lose any messages right now. My prcomail has hung and log says:
procmail: Executing "echo $YYMMDD > $YYMMDD_FILE"
procmail: [22600] Fri Oct 31 03:19:25 1997
procmail: Assigning "dummy="
procmail: Locking "/users/jaalto/.yymmdd.lock"
procmail: Executing "/users/jaalto/bin/cron.pls"
The code that run the cron.pls ( Perl script), has "w" flag and
explicit loackfile, so now procmail is waiting forever for
the program to terminate. And it's not going to terminate...
I assume that it's supposed to, but has a bug in it, no?
We have hundread servers down here and all just left to spend their
weekends and I have no idea on which server the code is executing.
I could do a rsh and grep all processes from all servers to find
out the hanging process, but does someone know an easier way
to find out where the programs are executed?
Assuming it's always the same one, you could add the following recipe to
the top of your .procmailrc:
:0
* ^Subject: host test message
{
LOG = $HOST
HOST
}
then send yourself a message with a subject of "host test message" and
watch the log. Don't forget to remove the recipe when you're done!
Philip Guenther