Date: Sat, 17 Dec 2011 10:20:48 -0600
From: Mike Brown <brown@mrvideo.vidiot.com>
To: cygwin mail list <cygwin@cygwin.com>
Subject: Re: cron log file empty
Message-ID: <20111217162048.GB23781@mrvideo.vidiot.com>
References: <20111217020908.GM14806@mrvideo.vidiot.com> <0LWC00DRZPRM70V2@vms173003.mailsrvcs.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0LWC00DRZPRM70V2@vms173003.mailsrvcs.net>
User-Agent: Mutt/1.5.17 (2007-11-01)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Sat, Dec 17, 2011 at 09:04:38AM -0500, Pierre A. Humblet wrote:
> cron logs to syslog, which by default uses the Windows log and which you 
> can read directly in Windows or filter with cronevents.

Good to know for the future.

> It's the first time I can recall where this is a problem, except for the 
> double entry in passwd. Do you use the crontab program to edit the crontab? 

Yes.  I've never hand edited the output file created by crontab, always
crontab -e.

> It makes sure all ownerships/permissions are correct.

Then it is doing a lousy job of it, otherwise it wouldn't bitch about
ownership permissions.

After I did a reboot, cron was no longer running as me, but as UID 0, so it
started complainging about ownership again.

As noted in a followup posting, I reverted back to 1.5 and all is well.

MB
-- 
e-mail: vidiot@vidiot.com | vidiot@vidiot.net            /~\ The ASCII
[I've been to Earth.  I know where it is.         ]      \ / Ribbon Campaign
[And I'm gonna take us there.    Starbuck  3/25/07]       X  Against
Visit - URL: http://vidiot.com/ | http://vidiot.net/     / \ HTML Email

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple