From owner-freebsd-hackers Tue Jan 14 06:53:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA16217 for hackers-outgoing; Tue, 14 Jan 1997 06:53:57 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA16207 for ; Tue, 14 Jan 1997 06:53:52 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id GAA26176 for ; Tue, 14 Jan 1997 06:54:38 -0800 (PST) Received: (qmail 14705 invoked by uid 110); 14 Jan 1997 14:53:00 -0000 Message-ID: <19970114145300.14704.qmail@suburbia.net> Subject: Re: truss, trace ?? In-Reply-To: from Andrew Stesin at "Jan 14, 97 06:43:37 pm" To: stesin@gu.net (Andrew Stesin) Date: Wed, 15 Jan 1997 01:53:00 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > This (IMHO) would be more "natural", 'cos there shouldn't be any "record" knowledge at that level. > > > Agreed. > > Best regards, > Andrew Stesin > > nic-hdl: ST73-RIPE You can fake record boundaries a number of ways, presume fixed record size: (1) choose the cycle size to be a multiple of the record size (2) once the file size has reached the cycle size, truncate by the size of the write. we presume that the write size equals the record size (which it does for struct /var/log/foo) -Julian