RE: CRON problems

["Harig, Mark" <maharig at idirect dot net>]

> 
> Hmm, seems to me like checking ownership and permissions of cron.pid
> would be something the cron_diagnose.sh should do.  What happened was
> that you ran it initially as your normal user account, and 
> the pid file
> was created.  Then when you tried to start it as a service, it was
> running as the SYSTEM account which didn't have permissions 
> to overwrite
> the file.  The solution would be to either just remove it and let cron
> recreate it, or "chown SYSTEM:SYSTEM /var/run/cron.pid".  
> Then you could
> give it more restrictive permissions than 777, perhaps 640 or 600.
> 

At present, the diagnostic script only checks for the existence of
/var/run/cron.pid and, if found, suggests that the user delete it
before reinstalling/restarting the cron service.

I agree that the script should check for SYSTEM.SYSTEM ownership
and 640 permissions, but I have not been able to find any
documentation specifying this.  Can anyone please point me to
some that specifies what the ownership and permissions of cron.pid
should be?  Of course, if users simply do what cron_diagnose.sh
suggests today, that should resolve this particular problem (i.e.,
not being able to write to the cron.pid file).

---

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