Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!europa.clark.net!newsfeed.internetmci.com!in2.uu.net!165.254.2.53!nonexistent.com!not-for-mail From: le@put.com (Louis Epstein) Subject: Re: /var/log/messages stopped??? X-Newsreader: TIN [UNIX 1.3 950824BETA PL0] X-Complaints-To: Email abuse@news2.new-york.net if this posting is inappropriate Lines: 18 Organization: Putnam Internet Services Message-ID: <EB4qI1.9LK@nonexistent.com> References: <338bb125.441417284@207.126.101.81> <338E60FE.8B@OntheNet.com.au> X-Trace: 865223206 7725 le [165.254.191.2] X-Nntp-Posting-Host: main.put.com Date: Mon, 2 Jun 1997 03:46:48 GMT Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42020 Tony Griffiths (tonyg@OntheNet.com.au) wrote: : Daniel Walton wrote: : > : > I have been doing some work on a FreeBSD system that required me to : > change the root crontab. I first checked the root crontab but I : > didn't find anything in it. Maybe I didn't look good enough because : > about the same time I changed the root crontab the /var/log/messages : > file stopped updating. Is this related to the crontab and how do I : > get this going again? : : No, no relation at all. The file "/var/log/messages" is written to by : syslogd which gets it's input from the "/dev/log" device. You havn't : played with anything in /dev or managed to kill of syslogd by any : chance? I've run into this even if I ran out of RAM making syslogd die. This doesn't just kill /messages,it also kills /adduser(a real headache for an ISP!) and I'd guess any other /var/log/ updating.