# ./utl/init-cron.sh Using password: V3feQz7iPPrB The cron daemon can run as a service or as a job. The latter is not recommended. Cron is already installed as a service under account .\cyg_server. Do you want to remove or reinstall it? (yes/no) OK. The cron service was removed. Do you want to install the cron daemon as a service? (yes/no) Enter the value of CYGWIN for the daemon: [ ] You must decide under what account the cron daemon will run. If you are the only user on this machine, the daemon can run as yourself. This gives access to all network drives but only allows you as user. To run multiple users, cron must change user context without knowing the passwords. There are three methods to do that, as explained in http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1 If all the cron users have executed "passwd -R" (see man passwd), which provides access to network drives, or if you are using the cyglsa package, then cron should run under the local system account. Otherwise you need to have or to create a privileged account. This script will help you do so. Do you want the cron daemon to run as yourself? (yes/no) Were the passwords of all cron users saved with "passwd -R", or are you using the cyglsa package ? (yes/no) Finding or creating a privileged user. The following accounts were found: 'cyg_server' . This script plans to use account cyg_server. Do you want to use another privileged account name? (yes/no) Account cyg_server already exists. Checking its privileges. INFO: cyg_server is a valid privileged account. INFO: The cygwin user name for account cyg_server is BEDL8-ACLARK+cyg_server. Running cron_diagnose ... ... no problem found. Do you want to start the cron daemon as a service now? (yes/no) cygrunsrv: Error starting a service: StartService: Win32 error 1069: The service did not start due to a logon failure. In case of problem, examine the log file for cron, /var/log/cron.log, and the Windows event log (using /usr/bin/cronevents) for information about the problem cron is having. Examine also any cron.log file in the HOME directory (or the file specified in MAILTO) and cron related files in /tmp. If you cannot fix the problem, then report it to cygwin@cygwin.com. Please run the script /usr/bin/cronbug and ATTACH its output (the file cronbug.txt) to your e-mail. WARNING: PATH may be set differently under cron than in interactive shells. Names such as "find" and "date" may refer to Windows programs.