Re^6: Cron Jobs That Run For Too Long

This trick was referenced many times in the following years, and many people won't bother to read the OP.

And personally I take "cron" as a generic term and I've also already seen people installing a cron demon on Win.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

Comment on Re^6: Cron Jobs That Run For Too Long

Replies are listed 'Best First'.
Re^7: Cron Jobs That Run For Too Long by Bod (Parson) on Apr 24, 2021 at 11:56 UTC
And personally I take "cron" as a generic term Interesting...I always use CRON in a nix context. Perhaps because, until the recent Raspberry Pi Curtain Controller, the only time CRON and I came together was on a webserver. I've also already seen people installing a cron demon on Win* I have heard rumours about this...it's not something I've looked into.	[reply]
Re^8: Cron Jobs That Run For Too Long by LanX (Saint) on Apr 24, 2021 at 15:34 UTC
Perl aims to be OS agnostic but was born on Unix and is heavily borrowing from Unix tools like bash, sed and awk plus wrapping many C functions from that OS. In case of conflicting terminology we fall back to basic Unix terms, like "directory" instead of "folder" The docs on the other hand are expected to mention platform issues, at least by pointing to perlport `flock` is an anti-example, that's why I started this meditation . > Interesting...I always use CRON ... 8.6 million google hits for "cron Windows" Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]