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