Date: Sun, 9 Nov 2008 10:06:30 -0500 From: "Michael P. Soulier" <msoulier@digitaltorque.ca> To: "Jeremy Chadwick" <koitsu@freebsd.org> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: debugging cronjobs not running Message-ID: <fb6605670811090706y34d3dd8cw8af4d207a2b35e2f@mail.gmail.com> In-Reply-To: <20081109123640.GA39105@icarus.home.lan> References: <fb6605670811090357i7223fa23h4bf6cab5bb3b3da3@mail.gmail.com> <20081109123640.GA39105@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 9, 2008 at 7:36 AM, Jeremy Chadwick <koitsu@freebsd.org> wrote: > I'm not sure why you sent this to me directly, but I do appreciate you > CC'ing the mailing lists. :-) Old thread, my bad. > No, this has never happened to me, or on any of the systems I've > administrated. Found it. The problem was several things. 1. The 6.3 upgrade merged in a HOME of /var/log in crontab, which broke some $HOME references in some of my jobs. 2. My /etc/aliases.db hadn't been used in some time, /etc/mail/aliases.db was. All fixed. The parse error in the debug was apparently not service affecting. I suspect it's looking for environment variables set before the command to run, judging by some of the code snippets I looked at. Mike -- Michael P. Soulier <msoulier@digitaltorque.ca> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fb6605670811090706y34d3dd8cw8af4d207a2b35e2f>