I have also read tips from folks who use at(1) to schedule the
"safety net" firewall restoration, as opposed to using a cron(8)
job. at(1) is more suited to one-shot scheduled jobs, and it is
a little easier to tell it "run this ten minutes from now", for
changing values of now.
At 05:58 PM 12.13.2003 +0100, Daan Vreeken [PA4DAN] wrote:
>On Saturday 13 December 2003 17:25, Jack L. Stone wrote:
>> Dear list:
>> I manage a remote gateway/nat/router/fw server where it is not convenient
>> for anyone to go downtown to the colo and do reboots.
>>
>> I've managed to do everythin
On Saturday 13 December 2003 17:25, Jack L. Stone wrote:
> Dear list:
> I manage a remote gateway/nat/router/fw server where it is not convenient
> for anyone to go downtown to the colo and do reboots.
>
> I've managed to do everything here remotely from my own console, including
> reboots when upd
Dear list:
I manage a remote gateway/nat/router/fw server where it is not convenient
for anyone to go downtown to the colo and do reboots.
I've managed to do everything here remotely from my own console, including
reboots when updating the OS requires it -- that is except when
reconfiguring the na
