More on the scheduler...

[Andy Poling <andy@jhunix.hcf.jhu.edu>]

To follow up on the thread that I started a while back, I have verified
that while message age SEEMS to get carried over from one instance of
scheduler to the other, the messages NEVER get expired.  It may sound
wierd, but it looks as though the new scheduler, when started up, cannot
cross day boundaries properly.  This might be best illustrated by an
example:

If I have certain messages (oh, say SMTP) set to expire after 3 days, and
I have a new scheduler starting each night, mailq will never show less
than 2 days remaining to expiration.  And the messages will never get
expired. 

On another note...  though I can't propose a fix, and it is not really a
dangerous problem... If you are running multiple routers in parrallel and
the first router dies (say from a segmentation fault), because that is the
PID in the .router.pid file, mailq will report that there is no router
running - even though there may still be numerous others running.  Like I
said, not exactly life-threatening - just a little scary the first time I
encountered it.

-Andy

Andy Poling                              Internet: andy@jhunix.hcf.jhu.edu
UNIX Systems Programmer                  Bitnet: ANDY@JHUNIX
Homewood Academic Computing              Voice: (410)516-8096    
Johns Hopkins University                 UUCP: uunet!mimsy!aplcen!jhunix!andy