Apparently, though unproven, at 00:14 on Tuesday 25 January 2011, Mark Knecht did opine thusly:
> On Mon, Jan 24, 2011 at 1:50 PM, Neil Bothwick <n...@digimed.co.uk> wrote: > > On Mon, 24 Jan 2011 10:59:16 -0800, Mark Knecht wrote: > >> Maybe a cron job that no matter what reloads the old rules 1 hour later? > > > > Wouldn't at make more sense? You don't want the thing to keep reloading > > your old config, at will do it once, and you can remove the task from the > > at queue once you successfully log back in. > > > > echo "command to reload old rules" | at now + 1 hour > > > > > > -- > > Neil Bothwick > > As a one-off test absolutely. There's no such thing as a once-off test :-) "Oh shit, it's still not working after 19 retries, 6 hours work, and extensive googling" most definitely does exist. Maybe I'm just paranoid, or maybe I just screwed up myself too many times, but I'd feel safer with cron for this. Cancelling it when done is equally easy whether cron or at -- alan dot mckinnon at gmail dot com
