: Above and beyond the standard reporting programs -qstat and -qread, I
: haven't heard of anything especially. The question is, how do you want to
: constrain users?
:
: Is it X message per day, X messages in the queue at any one time, X
: megabytes per day, X megabytes in the queue at any one time? Will you need
: to keep a history of what they have done? Will you want to differentiate
: between users such as any lists or system processes you're running?
At the moment, I was thinking of X MB in the queue at any one time.
At history would be nice, but not necessary. I can always find my own way log
logging but it would usually be nice to see a standard, fast way of doing it.
I'll have to examine cyclog and see if it does the kinds of things I'm looking
for.
In general, no I wouldn't want to differentiate between the users. This is
a system of three Linux boxes tasked with the large mail requirements for a
client who primarily uses NT. For the most part they don't know how or what
to do on the systems and they don't mind that at all. Almost everything they
do is from some automated interfaces I set up.
--
Matthew Harrell Hackers are just a migratory
Simulation Technology Division, SAIC lifeform with a tropism for
[EMAIL PROTECTED] computers.
