Date: Tue, 14 Jan 1997 18:51:47 +0200 (EET) From: Andrew Stesin <stesin@gu.net> To: Mikael Karpberg <karpen@ocean.campus.luth.se> Cc: Brian Somers <brian@awfulhak.demon.co.uk>, hackers@freebsd.org Subject: Re: Cyclic filesystem (WAS: Re: truss, trace ??) Message-ID: <Pine.BSF.3.95.970114184754.860e-100000@trifork.gu.net> In-Reply-To: <199701140207.DAA12321@ocean.campus.luth.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 14 Jan 1997, Mikael Karpberg wrote: > > I for one couldn't care less how good the implementation is. I would just > like a nice efficient way of making any logfile max out at a certain size, > plus minus a little. Exactly. I'm sure that even if your requested arbitrary size of a cyclic file will be rounded to a FS blocksize boundary by the implementation -- no problem at all. > I think you could just say that when you filled one > block (no matter what blocksize you run on the disk) and you need to > add a new one to the file, just grab the first block, remove it from the > front, clear it, append it to the end and start filling in data. Mininum > cyclic filesize, two blocks. Always cut at full blocksizes. I wholeheartly second your approach. > No matter what you might think of this, in terms of uggliness of such a hack, > I think it would be a really nice extention to the normal file system, if Be it "ugly" or not -- it's useful... [...] Best regards, Andrew Stesin nic-hdl: ST73-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970114184754.860e-100000>