From owner-freebsd-hackers Tue Jan 14 08:59:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id IAA22660 for hackers-outgoing; Tue, 14 Jan 1997 08:59:47 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id IAA22653 for ; Tue, 14 Jan 1997 08:59:45 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id JAA29888; Tue, 14 Jan 1997 09:46:17 -0700 From: Terry Lambert Message-Id: <199701141646.JAA29888@phaeton.artisoft.com> Subject: Re: truss, trace ?? To: brian@awfulhak.demon.co.uk (Brian Somers) Date: Tue, 14 Jan 1997 09:46:17 -0700 (MST) Cc: terry@lambert.org, stesin@gu.net, karpen@ocean.campus.luth.se, hackers@freebsd.org In-Reply-To: <199701140114.BAA11572@awfulhak.demon.co.uk> from "Brian Somers" at Jan 14, 97 01:14:49 am X-Mailer: ELM [version 2.4 PL24] 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 > > Cyclic file types imply record orientation. > [.....] > > Unless of course you don't mind having a truncated line at the start > of your log ;) > > This (IMHO) would be more "natural", 'cos there shouldn't be any > "record" knowledge at that level. "Natural" for text files, maybe. For the wtmp file, it's not so natural... it's wierd, even, since you can't resync to a valid record boundry without sync data built into the data format. For text files, the sync data can be "after the first \n", since it is a variable length record format with "\n" record seperators, but how do you resync wtmp? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.