Changes

|-

|-

| RetryAfter

| RetryAfter

| seconds >= 0

| secondes >= 0

| no

| non

| 900

| 900

| when set to a value>0, wait RetryAfter seconds before re-running the job after an error. Only applicable with RetryAttempts>0

| Quand la valeur est > 0, Affa attend «RetryAfter» secondes avant de ré-exécuter la tâche après une erreur. Applicable seulement si «RetryAttempts» > 0.

|-

|-

| RetryNotification

| RetryNotification

| yes ''or'' no

| oui ''ou'' non

| no

| non

| no

| no

| when set to no, Affa does not send an error message when a job has failed and RetryAttempts is configured. An error message is only sent when the last attempt has failed.

| Quand la valeur est réglée à «non», Affa n'envoie pas de message d'erreur quand une tâche a échoué et que «RetryAttempts» est configuré (c-a-d > 0). Un message d’erreur est envoyé seulement si la dernière tentative échoue.

|-

|-

| NRPEtrigger

| NRPEtrigger

| hours

| heures

| no

| non

| 24

| 24

| NRPE reports a job as critical when the last successful run is older then NRPEtrigger hours. To exclude the job from monitoring set to a value < 0.

| NRPE signale une tâche comme critique quand la dernière exécution réussie date de plus de «NRPEtrigger» heures. Pour exclure la tâche de ce contrôle, mettre une valeur négative.

|-

|-

| SambaShare

| SambaShare

| yes ''or'' no

| oui ''ou'' non

| no

| non

| no

| no

| Access to the job archives via CIFS protocol.

| Accès aux archives de la tâche via le protocole CIFS.

|-

|-

| SambaValidUser

| SambaValidUser

| local account

| compte local

| yes

| oui

| affa

| affa

| User who has permission to access the job archives via the CIFS protocol.

| Utilisateur(s) qui a(ont) la permission d'accéder aux archives de la tâche via le protocole CIFS.

|-

|-

| preJobCommand<br> preJobCommandRemote

| preJobCommand<br> preJobCommandRemote

| path relative to /etc/affa/scripts/

| chemin relatif vers /etc/affa/scripts/

| yes

| oui

| <none>

| <none>

| Scripts to be executed before a job run. The job name and type (scheduled, daily etc.) are passed as arguments to the program. The preJobCommandRemote scripts are copied to the remote server and then executed there. The scripts are executed in alphabetical order. Use a numerical prefix if you need a specific order e.g. 01scriptB, 02remotescriptA, 03scriptA. Use the included prescript-sample.pl and prescriptRemote-sample.pl as a starting point for own scripts.<br>'''Note:''' If you use the parameter “SMEServer=yes”, you may delete the “Included” relative to SME default directories in the jobconfig.ini: they will be backuped automatically.

| Scripts à exécuter avant le fonctionnement d'une tâche. Le nom de la tâche et le type («scheduled», «daily», etc.) sont passés en arguments au programme. The preJobCommandRemote scripts are copied to the remote server and then executed there. The scripts are executed in alphabetical order. Use a numerical prefix if you need a specific order e.g. 01scriptB, 02remotescriptA, 03scriptA. Use the included prescript-sample.pl and prescriptRemote-sample.pl as a starting point for own scripts.<br>'''Note:''' If you use the parameter “SMEServer=yes”, you may delete the “Included” relative to SME default directories in the jobconfig.ini: they will be backuped automatically.

|-

|-

| postJobCommand<br> postJobCommandRemote

| postJobCommand<br> postJobCommandRemote