> Cron is terrible. Paul Vixie says so himself. Get over it. "cron" does not[1] necessarily imply vixie-cron. A variety of implementations are available that h

> Cron is terrible. Paul Vixie says so himself. Get over it. "cron" does not[1] necessarily imply vixie-cron. A variety of implementations are available that have different feature sets. What exactly do you not like about cron the concept, and how are you running periodic events without > HUP ... listening for an event HUP is an "event". What is this "event" you want to listen for that requires junking HUP support? A new event type that tells the daemon the same information is just as kludgey as sending SIGHUP while adding unnecessary complexity. You can listen for an inotify event (or similar) on relevant file handles if you want, but that isn't applicable in all cases. If your complaint is that some daemon doesn't support something like inotify, file a feature request or send patches. HUP has the advantage that it is well-known, and you probably probably still want a way to force a daemon to re-read it's configuration even if you are already detecting changes with inotify/whatever. [1] I use fcorn ( http://fcron.free.fr/ http://fcron.free.fr/ )