Path: utzoo!attcan!uunet!cs.utexas.edu!chinacat!sequoia!rpp386!jfh From: jfh@rpp386.cactus.org (John F. Haugh II) Newsgroups: comp.unix.internals Subject: Re: Trojan Horses Message-ID: <18619@rpp386.cactus.org> Date: 23 Oct 90 12:40:26 GMT References: <1990Oct18.121818.9956@athena.mit.edu> <35111@cup.portal.com> Reply-To: jfh@rpp386.cactus.org (John F. Haugh II) Organization: Lone Star Cafe and BBS Service Lines: 16 X-Clever-Slogan: Recycle or Die. In article <35111@cup.portal.com> ts@cup.portal.com (Tim W Smith) writes: >This sounds like very bad file system design. If you are over some quota, >the write() that caused you to go over the quota should return an error. >The local system should determine your quota and remaining space and >check this on each write. you have just required that all write() operations be performed synchronously. there are open flags defined to support synchronous i/o - use them, or tell your vendor to include them in your version of the o/s, but don't hobble applications that aren't as serious about their output as yours. -- John F. Haugh II UUCP: ...!cs.utexas.edu!rpp386!jfh Ma Bell: (512) 832-8832 Domain: jfh@rpp386.cactus.org "SCCS, the source motel! Programs check in and never check out!" -- Ken Thompson