This is the mail archive of the
mailing list for the Cygwin project.
Re: cron problem
- From: Michael Adler <adler at glimpser dot org>
- To: Sanjay Gupta <SGupta at Epylon dot com>
- Cc: "'cygwin at cygwin dot com'" <cygwin at cygwin dot com>
- Date: Thu, 28 Feb 2002 10:49:51 -0500 (EST)
- Subject: Re: cron problem
I reported a related problem a few weeks ago and then reported a fix for
this last week.
Unfortunately, I haven't seen any response from the maintainers--perhaps I
reported this to the wrong list...
Did you start the cron daemon (as some other user?) before creating a
crontab? If yes, then that other user (probably 'SYSTEM') owns /var/cron
and you don't have write access.
On Win2k, you can change the owner of that directory, and then add that
user and give that user full control over /var/cron and /var/cron/tabs.
Next time, make a crontab before starting the cron daemon.
What I think should really happen is that cron should create those
directories during installation so they are owned by whoever installed
Best of luck.
On Wed, 27 Feb 2002, Sanjay Gupta wrote:
> Date: Wed, 27 Feb 2002 17:31:05 -0800
> From: Sanjay Gupta <SGupta@Epylon.com>
> To: "'firstname.lastname@example.org'" <email@example.com>
> Subject: cron problem
> Why, I am getting the following error when creating cronjobs.
> $ crontab -e
> no crontab for Administrator - using an empty one
> crontab: installing new crontab
> crontab: error renaming tabs/tmp.000107 to tabs/Administrator
> rename: Permission denied
> crontab: edits left in /tmp/crontab.107
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html