Path: utzoo!utgpu!water!watmath!clyde!att!ihu1h!ihnp4!ihlpe!daryl From: daryl@ihlpe.ATT.COM (Daryl Monge) Newsgroups: comp.unix.wizards Subject: Re: checking close's return value Message-ID: <3542@ihlpe.ATT.COM> Date: 25 Sep 88 02:41:09 GMT References: <20981@watmath.waterloo.edu> <1988Sep20.230150.7574@utzoo.uucp> <1213@unmvax.unm.edu> Reply-To: daryl@ihlpe.UUCP (Daryl Monge) Organization: Engineering Design Process Department, AT&T Bell Labs Lines: 14 In article <1213@unmvax.unm.edu> mike@turing.unm.edu (Michael I. Bushnell) writes: >UNIX does *not* guarantee that hardware related errors >will get reflected on write. This is one of its deficiencies, but is >unavoidable given the implementation of the filesystem. The actual >disk write may take place hours after the write(2) system call >(assuming update isn't running). So true. I would like it if close(2) would insure all blocks were successfully written to disk before it returned. (Possibly by an fcntl(2) option if every one doesn't want this?) Daryl Monge UUCP: ...!att!ihcae!daryl AT&T CIS: 72717,65 Bell Labs, Naperville, Ill AT&T 312-979-3603