At 15:57 2002-02-06 -0500, Tim Holmes wrote:
First off. Thanks for all the help. I'm starting to get to the bottom
of this. (I think.)
I set VERBOSE=on, and then ran some test messages and had some colleauges
send some test messages. Here's the end of what happened.
The _end_ is useless here. You want to know what recipes the warning is
appearing near (as the result of).
Besides just reviewing your rcfile for recipes that have constructs similar
to what I showed (which would generally be a good idea to just _try_
doing), have you considered fishing up one of the messages which you saw
actually trigger these warnings, and pump it into procmail again?
It runts through a whole mess of stuff since my ~/.procmailrc is like 450
lines long, and then ends there. When I see that, that's a good thing I'm
assuming?
The warnings are non-fatal. Showing the very end of the logfile does
nothing for isolating where the warnings are being generated.
that means that it created the lock file, found a match, then removed the
lock file. Is that correct? Or am I still not grasping this? (Long
rough day, it is very well possible!)
The lockfile you see mentioned isn't the lockfile which you're getting
warnings for.
So I need to find out what message is creating the lock file, and then nore
removing it? Am I on the right path now?
Since you saw multiple warnings, it would go to say that you've got
multiple recipes with extraneous locallockfiles. Or you may INCLUDERC a
filter multiple times.
The uptime in signature was just kewl when I first saw/set it up. I've
since forgot it was even there. At one point I even boasted an uptime
of like 160 days.
Write back when you have an uptime over 497 days (when the 32-bit jiffy
counter rolls over because jiffies are 1/100 of a second - do the
math. There are patches available for supporting a 64-bit jiffy counter
though). When that happens to you the first time, you do a doubletake
because you think that the server was rebooted without your knowledge,
which is bad news when you know the server doesn't just go down.
All my server restarts have been due to planned hardware upgrades (can't
swap to a new sysboard unless you reboot apparently).
Recent power outages, server rebuild wiped that clean though.
Uhm, time to think about getting yourself a UPS, and for the retentive,
backing that up with a generator. With the rolling blackouts in California
last year (I'm still in the block that is "next" to go), I went and set up
(and tested) a backup generator to power my entire house in the event of an
outage:
<http://www.professional.org/power/>
Not big and industrial, but I don't plan on having any outages if I can
help it.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail