3 ms·

Nice, I hear you on the risks of depending on 3rd-party libraries where you can't get your changes merged. It's nice to be able to roll your own in that case.

Nice, I hear you on the risks of depending on 3rd-party libraries where you can't get your changes merged. It's nice to be able to roll your own in that case. On the cron case, what are your thoughts on the email notifications? In what ways are the useful or useless? I'm not an expert in this stuff. And I really like the look of uback. I have the kind of sense (and pride) that maybe this thread I posted is going to be the place where some people (who were maybe previously laboring on something in obscurity) first posted it to the world, or mentioned about it. Or maybe were even encouraged by this Ask post, or seeing other people post work, to post their own work. I'd love it if that were the case, if this post of mine was something that contributed to people posting their work that went on to become something good. :) Not trying to give you pressure, but uback could be that. :) It's pretty fresh

slooonz 6y ago
> On the cron case, what are your thoughts on the email notifications? In what ways are the useful or useless? I'm not an expert in this stuff. I really dislike it. It’s probably the biggest pain point in cron IMO. 1. At the age of DKIM, DMARC and SPF, setting up a working MSA on every server that runs cron can be a real pain. Not always, it depends on the exact situation, but it can be. 2. The biggest issue is that it sends a mail whenever the cron job outputs anything, even if it is successful (exit code 0). This is batshit insane. 3. Nowadays, mail only notification are a bit limitating anyway.
- graderjs 6y ago
  Yeah, I suppose you could send the mail to an intermediary and filter it. But I agree with you. I have a 5 minute cron on my server, and when I login to root. "You have 4487 messages". Thanks, cron! :P :) xx
- pR0Ps 6y ago
  For 2, see chronic[0] (part of moreutils[1]). It runs a command, muting stdout and stderr unless the command exits with a non-zero status. [0]: https://manpages.debian.org/jessie/moreutils/chronic.1.en.html https://manpages.debian.org/jessie/moreutils/chronic.1.en.ht... [1]: https://joeyh.name/code/moreutils/ https://joeyh.name/code/moreutils/

slooonz 6y ago

> On the cron case, what are your thoughts on the email notifications? In what ways are the useful or useless? I'm not an expert in this stuff. I really dislike it. It’s probably the biggest pain point in cron IMO. 1. At the age of DKIM, DMARC and SPF, setting up a working MSA on every server that runs cron can be a real pain. Not always, it depends on the exact situation, but it can be. 2. The biggest issue is that it sends a mail whenever the cron job outputs anything, even if it is successful (exit code 0). This is batshit insane. 3. Nowadays, mail only notification are a bit limitating anyway.

graderjs 6y ago
Yeah, I suppose you could send the mail to an intermediary and filter it. But I agree with you. I have a 5 minute cron on my server, and when I login to root. "You have 4487 messages". Thanks, cron! :P :) xx
pR0Ps 6y ago
For 2, see chronic[0] (part of moreutils[1]). It runs a command, muting stdout and stderr unless the command exits with a non-zero status. [0]: https://manpages.debian.org/jessie/moreutils/chronic.1.en.html https://manpages.debian.org/jessie/moreutils/chronic.1.en.ht... [1]: https://joeyh.name/code/moreutils/ https://joeyh.name/code/moreutils/