[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: transports directory



Since I haven't upgraded from ZMailer 2.2 to ZMailer 2.99.xx, because of the
unreliability (see the archives!), I can't say that i'd be real tempted to
upgrade if you rewrote the scheduler.

Since i'm acting as a gateway for all of Xerox, Fuji Xerox, and Rank Xerox, I
don't think there's a timezone that I don't have correspondents in -- so I
can't afford to run code that crashes periodically, and requires attention when
I get to work in the morning.

>  Basically, all that would be eliminated would be the management of the
> channel directories in scheduler/* (automatic creation and deletion, etc).

But if this is all you're talking about eliminating, it's got to be such a
miniscule part of the disk I/O it can't possibly be worth it....   Since I
*always* have "smtp" messages in the queue (and "hold" messages in the queue),
the channel directories never come and go.   If a machine is emptying the
queues, then it should have cycles available to create/delete the directories.

So what am I missing?

Keep in mind, also, that you do want to create the files somewhere else, and
then link them into the directory where the scheduler is going to look at them,
because you can't afford to have the scheduler start to look at a file that is
not complete yet.

					\nick