IMHO quotas on /var/spool are a bad idea. They are only effective (as you have discovered) if the user owns the file there - many processes (news, mail, etc.) put things in spool with the ownership other than the user who the file is for. If you do get say all the processes to put the file in spool with the owner as the user, and the user spools a postscript print job, they can't get mail, news, whatever until the print job is removed. If the user is using gs to render the postscript, they may need additional space (in /var/spool) before that happens.
I grant that what I describe has a lot of if this statements. My experience with computers has shown me that eventually you get discover about 5 times the what if statements in actual problems. A solution would be to have quotas on the user's home directory, and have the user's mail spool to ~/mail or some such directory. Of course if the user fills up his home directory then he can't get any mail, but that is his/her problem ;-) Pat Ouellette Email: [EMAIL PROTECTED] Amateur Radio (voice): KB8PYM on KB8YVY repeater (52.650 / 146.835 / 444.650) Amateur Radio (packet): [EMAIL PROTECTED] Running down the hall: Hey you! You can ping your node, you can ping you neighbor, but you can't ping your neighborÂ’s node. > -----Original Message----- > From: Chris [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 29, 1998 9:29 PM > To: debian-user@lists.debian.org > Subject: Quota on Mail systems > > > > Hi. > > I am trying to implement quotas on the mail system of my debian linux > server. I have configured the quota system so that users have a quota on > /var/spool. > > This quota works fine and enforces the limit correctly when a user > attempts to put any files in that filesystem via the shell - but when a > user recieves mail it is placed into their mail file - regardless of their > disk quota. So affectively the mail system is quotaless. > > Can anybody explain this behaviour and perhaps suggest how I may correct > this?? > > Thanks, > > Chris > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]