Cron jobs won't run with network drive
Wed Dec 12 10:48:00 GMT 2001
You might find something in the mailing list archives if you had an idea
about where to start. I found this tidbit because I already know what
the problem is- I searched for "cron system site:cygwin.com" at
google.com (this is also in the first five lines of the
"On NT/W2K run cron under SYSTEM account as service to use that feature.
Note that you don't have access to net shares in the child processes"
I think the problem is with the SYSTEM account being used to start the
cron service. This is the default behavior for services, because the
system account has some special privileges need to run a service. You
can find these special rights in the
/usr/doc/Cygwin/inetutils-x.x.x-README. Maybe they are in the
cron.README as well, but then you already know them because you have
vigorously studied the cron readme to get it working already, right :-)
Basically, the SYSTEM account cannot access network drives. I don't
think there is any way for it to access any network drive at all ever.
So your choice is probably to create a new user that can access network
drives and has rights equivalent to SYSTEM (although I'm told that this
is *very* dangerous, YMMV).
Lamar Seifuddin wrote:
> Hello All,
> I researched this post and followed the instructions
> I can create cronjobs on the local drive
> but, I can't seem to do anything with cronjobs which
> involve accessing the network drives.
> Anyone have an idea of what I'm missing?
> Appreciate any help in this matter.
> thank you,
> -----Original Message-----
> From: Cioffari, Joseph [mailto:Joseph.Cioffari@aig.com]
> Sent: Tuesday, August 21, 2001 10:57 AM
> To: 'firstname.lastname@example.org'
> Subject: FW: Cron jobs won't run
> I followed instructions below but I am now having problems writing and/or
> creating the 'Administrator' crontab file. It is giving me 'writing
> /tmp/cron135 permission denied' responses. I even changed all permissions
> on the /tmp and /var/cron directories so that Administrator could write to
> it after it didn't seem to work with SYSTEM owning those directories. Any
> -----Original Message-----
> From: Headley, Kent [mailto:email@example.com]
> Sent: Monday, August 20, 2001 7:23 PM
> To: Cioffari, Joseph
> Subject: Re: Cron jobs won't run
> hello joe,
> I had this problem as well; I do know that part of the solution is to
> install cron using
> cygrunsrv -I cron -p /usr/sbin/cron.exe -a -D -e "CYGIWIN=tty ntsec"
> and/or defining 'CYGWIN=tty ntsec' in your NT environment variables.
> Another problem that I encountered was that the directory /var/cron/tabs
> must be created by the cron service to make sure that all of the permissions
> work correctly. Note that crontab will also create this directory if it
> doesn't exist, but will not set the owner, group or permissions correctly.
> To make this work correctly, first remove the /var/cron and all below it:
> rm -Rf /var/cron
> and then start the cron service (it will automatically create
> /var/cron/tabs, owned by SYSTEM)
> cygrunsrv -S cron
> Only now is it safe to run crontab to install, remove or edit cron jobs.
> I hope this helps.
> Kent Headley
> Software Engineer
> Research & Development Division
> 7700 Sandholdt Road
> Moss Landing, CA 95039-0628
> Tel: 831.775.1822
> Fax: 831.775.1645
> e-mail: firstname.lastname@example.org
> website: http://www.mbari.org
> "If at first the idea is not absurd, then there is no hope for it." - Albert
> 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/
Your mouse has moved.
Windows NT must be restarted for the change to take effect.
Reboot now? [OK]
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
More information about the Cygwin