From owner-freebsd-questions@FreeBSD.ORG Sat Nov 1 02:08:02 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B221106568B for ; Sat, 1 Nov 2008 02:08:02 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from QMTA09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by mx1.freebsd.org (Postfix) with ESMTP id 002B88FC18 for ; Sat, 1 Nov 2008 02:08:01 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from OMTA01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA09.westchester.pa.mail.comcast.net with comcast id ZTNF1a01k0EZKEL59e80iy; Sat, 01 Nov 2008 02:08:00 +0000 Received: from koitsu.dyndns.org ([69.181.141.110]) by OMTA01.westchester.pa.mail.comcast.net with comcast id Ze7x1a0042P6wsM3Me7xFs; Sat, 01 Nov 2008 02:07:58 +0000 X-Authority-Analysis: v=1.0 c=1 a=QycZ5dHgAAAA:8 a=0vTpi-7yqJd5uVFssW0A:9 a=zrON_DtxeKDrSyftT9uhHpxI1tMA:4 a=EoioJ0NPDVgA:10 a=LY0hPdMaydYA:10 Received: by icarus.home.lan (Postfix, from userid 1000) id C7841C9419; Fri, 31 Oct 2008 19:07:56 -0700 (PDT) Date: Fri, 31 Oct 2008 19:07:56 -0700 From: Jeremy Chadwick To: "Michael P. Soulier" Message-ID: <20081101020756.GA46968@icarus.home.lan> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-questions Subject: Re: crons and syslogd not running X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2008 02:08:02 -0000 On Fri, Oct 31, 2008 at 08:56:33PM -0400, Michael P. Soulier wrote: > I upgraded from 5.5 to 6.3, and I've noticed that many of my cronjobs defined > in /etc/crontab don't seem to be running anymore. I have nightly jobs that > obviously aren't running, and /var/log/cron makes no mention of them. > > Looking for logs, I found syslogd down, although cron was up. > > Any idea of where I should look? Stability problems in syslogd? "dmesg" might show something like syslogd crashing or segfaulting for some reason. And no, I've never experienced any stability problems with syslogd on FreeBSD (any version; 2.2.8 through 7.1). Otherwise, I'd say the upgrade may have gone awry at one particular stage of your upgrade. If the problem doesn't recur, I wouldn't worry too much about it. Upgrading between major versions always seems to have quirks/risks. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |