starting cron

[Harig, Mark]

> -----Original Message-----
> From: Pierre A. Humblet [mailto:pierre.humblet@ieee.org]
> Sent: Sunday, June 22, 2003 3:07 PM
> To: cygwin@cygwin.com
> Subject: Re: starting cron
> 
> 

(text deleted)

> P.S.: perhaps testing for uid=400 and gid=401 could be added
> to the cron diagnostic.
> 

OK.  Two new tests have been added: 

1. Check to see whether the user ID is 400 AND group ID is 401.
   If so, then notify the user that there might be a problem with
   /etc/passwd, along with instructions on how to fix the problem
   (i.e., 'mkpasswd -l -u [User ID] >> /etc/passwd' or 
          'mkpasswd -d -u [User ID] >> /etc/passwd'
   Provide the command-line option '-f' to force the script to
   skip this test and proceed with other tests.

2. Check to see whether the directory /var/run has adequate permissions
   so that a 'cron.pid' file may be created.  If permissions are
   insufficient, then notify the user about the problem and exit.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: cron_diagnose.sh
Type: application/octet-stream
Size: 6983 bytes
Desc: cron_diagnose.sh
URL: <http://cygwin.com/pipermail/cygwin/attachments/20030624/79c70d7a/attachment.obj>
-------------- next part --------------
--
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/