Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.uoknor.edu!news.nodak.edu!netnews1.nwnet.net!news.u.washington.edu!uw-beaver!uhog.mit.edu!news.kei.com!news.mathworks.com!tank.news.pipex.net!pipex!demon!youngman.demon.co.uk From: jeremy@youngman.demon.co.uk (Jeremy Youngman) Newsgroups: comp.unix.bsd.bsdi.misc Subject: bsdi v201 syslogd stops sending logs across network Date: Sat, 27 Jan 1996 15:58:08 GMT Lines: 15 Message-ID: <822758344.26179@youngman.demon.co.uk> NNTP-Posting-Host: youngman.demon.co.uk X-NNTP-Posting-Host: youngman.demon.co.uk X-Newsreader: Forte Free Agent 1.0.82 Hi, anybody out there having problems with syslogd (under bsdi v201) eventually stopping to send logs across the network? syslogd still seems to log to disk okay, and the network itself seems okay (we can send dns udp packets about) - but syslogd seems to stop sending log info to the main syslogd server (via udp, port 514?). If we restart syslogd (client side) then all goes well for a while (ie the server receives the logs) - then traffic suddently stops again (although other traffic, like dns udp, still flows okay). Replies preferred by email if possible. TIA