Apparently, cron is deprecated in OSX 10.5.
K, fine. But its replacement,
launchd, is a crappy replacement. It has no concept of time ranges (Or does it? Any mac folks with insight to share here?)
I want to replicate this crontab:
0,20,40 8-17 * * * /users/drallen/bin/thing.sh
So, run every 20 minutes between 8am and 5pm 5:40pm
(
Read more... )
Comments 9
Alternately, you could create a shell wrapper that says "Is it between 8 and 5? No? Quit!" but that seems ridiculous to have to do.
(P.S. Isn't StartInterval of 300... 5 minutes, not 20? Wouldn't you want 1200 instead? Also, I think your cron runs every 20 minutes from 8:00 - 5:40 PM.)
Reply
Reply
I can't help with the "why's cron broken" problem, alas.
Reply
Reply
Reply
I was also thinking that ls, rm, and ln are really kinda old concepts and should be replaced.
Oooh, and while we're at it, let's revamp grep to take completely new and different parameters.
This will help with usability, where usability is equivalent to proprietary offshoots of commonly used functionality to make Mac users more separate from other communities.
Grumbly, grumbly.
Reply
As for different grep parameters, at least we're sort of used to that with Solaris/GNU/whatever differences.
Cute userpic. :)
Reply
Reply
XML never seemed like a good idea to me. Human readable is one thing, the ability to have a generic syntax validator is cool, but it adds so much junk. One of my jobs at work is a process that takes a large database extract and rewrites about a fifth of it into XML.. creating a 5G file, which then gets compressed and sent via FTP over an already burdened connection. Daily.
The stuff you can do with XSLT is completely awesome, don't get me wrong. But I can do a heck of a lot with cut/sed/grep/perl on tab-delimited files.
Reply
Leave a comment