Re: Quota exceeded...

Tim Wright (timw@sequent.com)
Mon, 27 Jan 1997 11:46:45 PST

A somewhat reasonable approach to lessening the effect of such logging is
to put the process to sleep for a second each time it "causes" the error
message. That way, badly written user code doesn't kill the system.

t

In message <199701260127.UAA07621@jenolan.caipgeneral>,"David S. Miller" writes
:
> Date: Sun, 26 Jan 1997 01:20:28 +0000 (GMT)
> From: Chris Evans <chris@ferret.lmh.ox.ac.uk>
>
> Any chance of a printk() when a user's file write is stopped due to
> hitting a hard quota? Would be a nice thing to have
> logged. Although perhaps for messages like this and other future
> messages, we might consider a new log message reporting scheme.
>
> Be _really_ careful with this one. For many months we had to bother
> sun endlessly because Solaris in fact did this, so if some stupid user
> exceeded his quota and his process was just poorly written and kept on
> trying the writes etc. your machine goes into %99 system time doing
> console output.

--
Tim Wright, Worldwide Technical Services,         |  Email: timw@sequent.com
Sequent Computer Systems Inc., 15450,             |
SW Koll Parkway, Beaverton, Oregon 97006          |  Phone: +1-503-578-3822
"Applying computer technology is simply finding the right wrench to pound
in the correct screw"