Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!uakari.primate.wisc.edu!ames!pacbell!att!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.questions
Subject: Re: fopen ( ..., "a" ) --- how does the "a" work?
Message-ID: <1989Dec12.054345.1597@chinet.chi.il.us>
Date: 12 Dec 89 05:43:45 GMT
References: <3250@hub.UUCP> <1989Dec7.130813.4992@virtech.uucp> <11775@smoke.BRL.MIL> <1989Dec9.000805.1617@chinet.chi.il.us> <11785@smoke.BRL.MIL>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Organization: Chinet - Chicago Public Access UNIX
Lines: 20

In article <11785@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:

>-In article <11775@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
>->On a single-user non-multitasking system, a better implementation would
>->be to seek to the end only on the initial open, not for each write.
>-But what if the single-user non-multitasking system is networked to
>-a shared filesystem and you would like your log files to work?

>Suggest you look up "system" in a decent engineering textbook.
>You described a system that doesn't fit my qualifiers.


I fail to see how providing each user-level process with its own CPU
and i/o facilities would break anyone's concept of a "system".  Do
you mean that all filesystem clients and servers must maintain state
information to be worthy of being called a "system"?


Les Mikesell
  les@chinet.chi.il.us