7OK

Outils du site

Avoir fait du travail la source de l'entrée en humanité me semble une perversion. On a confondu, plus ou moins sciemment, le travail-torture et l'activité libérante. La générosité, le dévouement sont des attitudes plus anoblissantes que le courage au travail. [Albert Jacquerd]
Vous êtes ici : 7OK » Ⓦindows » Cygwin » Crontab
20-windows:50-cygwin:10-crontab

Différences

Ci-dessous, les différences entre deux révisions de la page.

Lien vers cette vue comparative

Les deux révisions précédentesRévision précédente
20-windows:50-cygwin:10-crontab [2016/11/16 16:30] – Roge20-windows:50-cygwin:10-crontab [2017/10/06 23:40] (Version actuelle) – modification externe 127.0.0.1
Ligne 1: Ligne 1:
 +====== Crontab ======
 +
 +===== Références =====
 +
 +[[http://linux.subogero.com/894/cron-on-cygwin/]]
 +
 +[[http://www.davidjnice.com/articles/cygwin_cron-service.html]]
 +
 +[[http://ehealth-aussie.blogspot.co.nz/2013/06/setup-cygwin-cron-service-on-windows.html]]
 +
 +===== Mode d'emploi =====
 +
 +Il faut installer les paquets :
 +  * cron
 +  * cygrunsrv
 +
 +Lancer ''cron-config''
 +
 +<code bash>
 +Roge@HAL ~
 +$ cron-config
 +Do you want to install the cron daemon as a service? (yes/no) yes
 +Enter the value of CYGWIN for the daemon: [ ] ntsec
 +
 +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) no
 +
 +Were the passwords of all cron users saved with "passwd -R", or
 +are you using the cyglsa package ? (yes/no) no
 +Attempting to find or create a privileged user.
 +No privileged account could be found.
 +This script plans to use the name cyg_server for the new user,
 +which will only be able to run as a service.
 +Do you want to use another name (not an interactive account)? (yes/no) no
 +
 +User cyg_server needs a password. It must match
 +the rules in force on your system.
 +Please enter the password for cyg_server:
 +Reenter:
 +
 +User 'cyg_server' has been created.
 +If you change the password, please keep in mind to change the
 +password for the cron service, too.
 +
 +
 +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,
 +<fc #008000>/var/log/cron.log</fc>, 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.
 +
 +</code>
 +
 +Do you want to install the cron daemon as a service? (yes/no) yes
 +Enter the value of CYGWIN for the daemon: [ ] ntsec
 +
 +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) no
 +
 +Were the passwords of all cron users saved with "passwd -R", or
 +are you using the cyglsa package ? (yes/no) no
 +Attempting to find or create a privileged user.
 +No privileged account could be found.
 +This script plans to use the name cyg_server for the new user,
 +which will only be able to run as a service.
 +Do you want to use another name (not an interactive account)? (yes/no) no
 +
 +User cyg_server needs a password. It must match
 +the rules in force on your system.
 +Please enter the password for cyg_server:
 +Reenter:
 +
 +User 'cyg_server' has been created.
 +If you change the password, please keep in mind to change the
 +password for the cron service, too.
 +
 +
 +Running cron_diagnose ...
 +... no problem found.
 +
 +Do you want to start the cron daemon as a service now? (yes/no) <fc #008000>yes</fc>
 +
 +OK. The cron daemon is now running.
 +
 +In case of problem, examine the log file for cron,
 +<fc #008000>/var/log/cron.log</fc>, 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.
 +Installer le service :
 +
 +''cygrunsrv -I Cygwin_CRON -p /usr/sbin/cron -a -n''     
 +
 +Ne jamais éditer directement le fichier /etc/crontab. Pour modifier la crontab lancer la commande :
 +
 +''crontab -e''
 +
  

Outils de la page