From owner-freebsd-questions Sat Jan 15 18:50:54 2000 Delivered-To: freebsd-questions@freebsd.org Received: from earth.wnm.net (earth.wnm.net [208.246.240.243]) by hub.freebsd.org (Postfix) with ESMTP id D2AE314CCA for ; Sat, 15 Jan 2000 18:50:51 -0800 (PST) (envelope-from alex@wnm.net) Received: from localhost (alex@localhost) by earth.wnm.net (8.8.8/8.8.8) with ESMTP id UAA06433; Sat, 15 Jan 2000 20:50:19 -0600 (CST) Date: Sat, 15 Jan 2000 20:50:19 -0600 (CST) From: Alex Charalabidis To: Evren Yurtesen Cc: FreeBSD Questions Subject: Re: is this a bug? In-Reply-To: <200001152311.SAA53209@cc942873-a.ewndsr1.nj.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 15 Jan 2000, Crist J. Clark wrote: > Evren Yurtesen wrote, > > Hello > > I got these messages in my /var/log/messages file > > > > Jan 15 18:58:01 dc su: rtprio 'root' (root): Invalid argument > > Jan 15 18:58:27 dc init: fatal signal: Segmentation fault > > Jan 15 18:58:57 dc init: fatal signal: Segmentation fault > > Jan 15 19:00:00 dc CRON[66566]: rtprio 'root' (daemon): Invalid argument > > Jan 15 19:00:00 dc CRON[66567]: rtprio 'root' (daemon): Invalid argument > > > > I could not understand what is the problem but it appeared to repeat > > every 5 minutes. > > Every time that atrun(8) is started in /etc/crontab? Coincidence? :) > No coincidence. That's the easy part. > > Then I sent a HUP signal to cron but it did not help. At last I decided > > to KILL the cron daemon and when I sent KILL signal everything returned > > back to normal. I did not get any more error messages even after 15 > > minutes. but then when I started cron again they started to repaeat every 5 > > minutes. I am using the standart crontab file distributed with FreeBSD > > When you stopped cron(8), it stopped running atrun(8) every five > minutes. > > > any ideas? > > Somebody's crontab or /etc/crontab have some messed up entries? Not > sure, never seen a message like those before. > I have, on 3.3-RC, but my memory of the incident is a bit vague. What *appeared* to solve it was deleting root's crontab. IIRC, it started happening after I edited /etc/crontab with a text editor, NOT crontab(1). Root did not have a crontab before that but it seems that one got added anyway, despite the fact that I didn't use crontab(1). It didn't make sense then and doesn't make sense now so don't ask me why. :) hth -ac -- ============================================================== Alex Charalabidis (AC8139) 5050 Poplar Ave, Ste 170 Systems Administrator Memphis, TN 38157 WebNet Memphis (901) 432 6000 ============================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message