>>> [EMAIL PROTECTED] wrote ...
> > How much is the performance degradation when you use AFS-based
> >central spool directory?
>
> This depends on the number of users and the amount of mail they receive.
> The AFS cacheing keeps breaking callbacks when the directory is updated,
> which in practice means whenever any user receives a mail message. We
> have at the moment over 5000 users in our cell, so a single central
> spool directory was pretty hopeless.
We're gonna make a spool directory for each user, for example
/afs/p/mail/spool/$user. The mail will be delivered into the directory.
Could the callback break still a problem in this case? I think it's not.
The reasons we need this kind of delivery mechanism are;
1. Keep the user's home untouched
2. Don't put any special ACL on the user's home
3. Standardize the locking methods among various MUA's
4. Manage and control any misbehaviors of delivering mails easily
5. Minimize user training and MUA changes (We can only reset the
environment variable $MAIL)
--
___________________________________________________________________________
_____ ___ __ __
__/\__ |_ _| / _ \ \ \_/ / Remember Yesterday, Dream about Tomorrow
\ / | | | /_\ | \ / but ... LIVE TODAY !!!
/_ _\ | | | _ | | |
\/ __| | | | | | | | [EMAIL PROTECTED] (Jae-young Kim)
|___/ |_| |_| |_| Researcher, Computer Center/POSTECH, KOREA
___________________________________________________________________________
