scheduler wish list

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

I think other people running ZMAILER at high-traffic sites have probably
run into this same shortcoming... 

The is scheduler's inability to maintain state from one instance to
another. If scheduler dies or the machine dies or is down for some reason,
all sense of message age disappears.  It would be super useful if
scheduler kept a record of the state of the messages on disk so that it
could pick up where it left off.  Naturally, this is a greater problem for
sites like us who are pushing the envelope (in numerous directions :-) but
it seems like a necessary feature given ZMAILER's stated design goals.  It
even already knows how to dump its state (hint - MAILQ and rendezvous
file) - all that remains is a method of reading it back and making use of
it. 

Does this sound reasonable?

-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