From owner-freebsd-questions@FreeBSD.ORG Tue Jun 17 17:32:59 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59BC237B401 for ; Tue, 17 Jun 2003 17:32:59 -0700 (PDT) Received: from malkav.snowmoon.com (malkav.snowmoon.com [209.23.60.62]) by mx1.FreeBSD.org (Postfix) with SMTP id 7E2E543FDF for ; Tue, 17 Jun 2003 17:32:58 -0700 (PDT) (envelope-from jaime@snowmoon.com) Received: (qmail 99558 invoked from network); 18 Jun 2003 00:32:57 -0000 Received: from localhost.snowmoon.com (HELO localhost) (127.0.0.1) by localhost.snowmoon.com with SMTP; 18 Jun 2003 00:32:57 -0000 Date: Tue, 17 Jun 2003 20:32:56 -0400 (EDT) From: Jaime To: Mike McGrath In-Reply-To: Message-ID: <20030617202509.B99528@malkav.snowmoon.com> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-questions@freebsd.org Subject: Re: Cron wacking out X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2003 00:32:59 -0000 > root: not found > Jun 17 00:20:00 silver-fox /usr/sbin/cron[247]: (root) CMD > (root^I/usr/libexec/atrun) I'm guessing, but it sounds a lot like cron is trying to execute "root" as a command. The ^I is probably a control character that go into a file somewhere by accident. You might want to cvsup/make-world in order to get correct files in place. BTW, when I last saw something like this, it was a bunch of ^L control characters scattered through my system's source code. The system in question had a bad mother board. I don't know if you have a problem like that, but you should keep your eyes open for an abundance of control characters in random places in random files. Even after cvsup-ing new source code files, I still had these ^L characters everywhere. So, look for a clue like that. Wow, that happened to me back when I was updating from 2.2.5 to 2.2.7. :) Thanks for the chance at nostalgia. :) Jaime