Timeline for Where is my logfile of crontab?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 17, 2023 at 8:38 | comment | added | ikrabbe | I think in classic cron daemons there actually was no idea of and no need for logging the operation of the cron daemon itself, as anything it did was to start a command on a time based schedule. So for diagnostics of a working cron daemon it is best to simply schedule a job and check it's output in some very near future. That way you also train to modify the crontab. But in the end you are right: The question is about the cron daemon itself. I just never had a use for that. | |
| Jul 1, 2023 at 13:12 | comment | added | maxschlepzig | OP is likely referring to the logging of the Cron daemon itself, whereas you are referring to the stdout/stderr handling of cron jobs. When a cron job time specification matches, a Cron daemon logs its job execution, i.e. even when it was successful. For example, cronie logs CMD/CMDEND including full command lines and user name. By comparing matching CMD/CMDEND lines you can compute the job's run time. | |
| S Jun 14, 2023 at 13:36 | history | edited | AdminBee | CC BY-SA 4.0 |
Minor formatting
|
| S Jun 14, 2023 at 13:36 | history | suggested | Benjamin Loison | CC BY-SA 4.0 |
Add Bash syntax highlighting
|
| Jun 13, 2023 at 18:51 | review | Suggested edits | |||
| S Jun 14, 2023 at 13:36 | |||||
| S Feb 8, 2018 at 7:07 | history | suggested | Stephen Fox | CC BY-SA 3.0 |
Added more detail to specifically explain crontab behavior differently from cron behavior.
|
| Feb 7, 2018 at 16:24 | review | Suggested edits | |||
| S Feb 8, 2018 at 7:07 | |||||
| Jun 26, 2015 at 8:56 | history | answered | ikrabbe | CC BY-SA 3.0 |