Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!mips!zaphod.mps.ohio-state.edu!rpi!uupsi!rice!bcm!soma!concurrent-request
From: lac@ecs.soton.ac.uk (Les Carr)
Newsgroups: comp.sys.concurrent
Subject: Submission for comp-sys-concurrent
Message-ID: <445@gazette.bcm.tmc.edu>
Date: 9 Apr 90 06:55:19 GMT
Sender: usenet@bcm.tmc.edu
Lines: 23
Approved: concurrent@soma.neuro.bcm.tmc.edu
           id aa08582; 26 Mar 90 13:14 BST
Responding-System: ecs.soton.ac.uk
Status: O

From: lac@ecs.soton.ac.uk (Les Carr)
Newsgroups: comp.sys.concurrent
Subject: Re: Where's syslog()?
References: <356@gazette.bcm.tmc.edu>
Organization: University of Southampton, UK

mark@sickkids.utoronto.ca (Mark Bartelt) writes:

>I'm porting a bunch of stuff from a 4.3bsd system to our Masscomp
>(currently running RTU 4.1A), and syslog() seems to be missing from
>libc, even though there's a syslog(3) man page.  Curiously, syslog.h

Hah! I got caught on this one a couple of months ago, submitted a bug
report and got a nice letter back several weeks later to say that the
bug would be fixed in future releases of the OS by deleting references
to 'syslog' from the manual. Fume. Smoulder.
-- 
---
	Foo

Articles to: concurrent@soma.bcm.tmc.edu or uunet!soma.bcm.tmc.edu!concurrent
Administrative stuff: concurrent-request@soma.bcm.tmc.edu
Stan Barber, Moderator