This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

cron bug


Hello,

Iâve set up cron as below on a fresh Windows 10 with a fresh, minimal 64-bit Cygwin installation. Cronjobs are not executed and cronevents says /usr/sbin/cron:
PID 608: (CRON) error (can't switch user context). The output of cronbug is attached.

 

When I run the service not under my own user but as an administrator, the result and error is the same.

 

Thanks! Any advice is appreciated.

 

 

$ cron-config

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 LocalSystem.

Do you want to remove or reinstall it? (yes/no) yes

OK. The cron service was removed.

 

Do you want to install the cron daemon as a service? (yes/no) yes

Enter the value of CYGWIN for the daemon: [ ] CYGWIN

 

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) yes

 

Running cron_diagnose ...

... no problem found.

 

Do you want to start the cron daemon as a service now? (yes/no) yes

OK. The cron daemon is now running.

 

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.

Attachment: cronbug.txt
Description: Text document

Attachment: signature.asc
Description: OpenPGP digital signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]