zlacker

The Debian package installer once asked me (a long long time ago) whether I want to restart sshd after a glibc update, saying existing sessions wouldn’t be affected. That was a lie, apparently, because the SSH session I was updating the system died and the resulting SIGHUP killed the update process in a way that necessitated some recovery later.

More seriously, Mikrotik routers have a nice feature where they will rollback your config change if the connection you’re configuring one over stops responding to keepalives. Like a lot of Microtik features, it’s probably copied from some Serious Business network OS, but I wouldn’t know.

>>manana+(OP)
Yes, the Safe Mode button. But you have to remember to press it before you start configuring the router and then exit Safe Mode when you're done.

>>manana+(OP)
it’s probably copied from some Serious Business network OS

I wouldn't know who came first, but it's a feature of JunOS (Juniper) as well: every config apply first applies the config, then waits for confirmation on the terminal where it was ran. If confirmation isn't given within X seconds, it reverts the config change.

>>tremon+pf
That only applies when you do "commit confirmed".

>>manana+(OP)
> Like a lot of Microtik features, it’s probably copied from some Serious Business network OS, but I wouldn’t know.

Not sure who came first, but OpenWRT does this if you make a breaking change in the webinterface, and connectivity is lost for 60 sec, it will rollback the changes.