Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!wuarchive!uunet!mcsun!cernvax!chx400!forty2!eschle From: eschle@forty2.physik.unizh.ch (Patrik Eschle) Newsgroups: comp.sys.alliant Subject: Re: programs with syslog Message-ID: <1414@forty2.physik.unizh.ch> Date: 3 Jan 91 10:39:00 GMT References: Organization: Physics Institute University of Zuerich, Switzerland Lines: 17 gjalt@es.ele.tue.nl complains about a problem with libc(syslog.o) and asks: >So is this just another example of having to compiling Unix yourself on an >Alliant? Yes, and an old one - we've reported this back in March 1990. Remove their syslog.o from libc and replace it by the BSD syslog.o. It took them almost a year from 5.5 to 5.6 - why don't they have 10 minutes to fix this trivial bug? Patrik -- Patrik Eschle, Physics Institute University of Zuerich (Switzerland) inet: eschle@physik.unizh.ch (bang: uunet!chx400!forty2!eschle) -> Send CHUUG mail to chuug@chuug.uu.ch <-