Downloads provided by UsageCounts
doi: 10.5281/zenodo.31049
Cron is a really useful tool, but if you're not careful, you end up with e-mail few minutes reporting that something was run. If you don't go through every last report examining it line by line, you might miss when something actually breaks. After years of putting up with it or writing wrapper scripts that silence output unless certain conditions are met, I've created a more generic wrapper that can : handle 'highlander' conditions kill commands that run too long silence output unless a non-zero exit status silence output unless something's sent to STDERR silence output if it matches acceptable patterns highlight lines that aren't in the list of patterns Note that this code is not yet released. My place of work has a formal 'software release' procedure that I'm still trying to work through
cron
cron
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
| views | 35 | |
| downloads | 1 |

Views provided by UsageCounts
Downloads provided by UsageCounts