Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpda!hpwala!hpwadac!lupienj
From: lupienj@hpwadac.hp.com (John Lupien)
Newsgroups: comp.unix.internals
Subject: Re: Ideas for changes to Unix filesystem
Message-ID: <1693@hpwala.wal.hp.com>
Date: 8 Feb 91 22:12:28 GMT
References: <1991Jan30.143326.16676@socs.uts.edu.au> <422@bria>
Sender: netnews@hpwala.wal.hp.com
Reply-To: lupienj@hpwadac.UUCP (John Lupien)
Organization: Hewlett Packard, Waltham, Mass
Lines: 15

In article <422@bria> uunet!bria!mike (Michael Stefanik) writes:
>In an article, socs.uts.edu.au!jeremy (Jeremy Fitzhardinge) writes:
>>3 - limited sized files
>Although this has some merit, I would much prefer to have cron fire
>up a script that simply trims down my growing log files, rather than
>burden the kernel with the job.

I quite agree that this does not need to be done in the kernel.
The original posting was talking about a kind of "fifo" file with
the data falling off a cliff when it gets to the end. This could
be done quite nicely at the user level with a file-based ring buffer.

---
John R. Lupien
lupienj@hpwarq.hp.com