Boston Linux & UNIX was originally founded in 1994 as part of The Boston Computer Society. We meet on the third Wednesday of each month, online, via Jitsi Meet.

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] SysVinit vs. systemd



On Wed, Sep 17, 2014 at 10:53 AM, Bill Bogstad <bogstad at pobox.com> wrote:
> a trend
> away from debugging problems and towards just doing reinstalls/restarts.   I
> think the rise of virtualization (particularly in the cloud) has
> driven this.   As the
> tools make it easier and easier to spin up a new VM, why bother to figure out
> what caused the old one to fail, just reinitalize a new one and keep going.

With virtualization (and multi-instance scale-out), it's not a
disjunction: you can do BOTH (as someone pointed out up-thread). If
you autostart a replacement instance (or just shift load to a N/N+m
survivor) and keep the failed offline, you can debug at leisure while
continuing/restoring service.

[ how much debugging you can do off-line with it cut off from other
tiers is a separate question, but you can at least collect 'forensics'
that will be destroyed at re-start. ]
-- 
Bill Ricker
bill.n1vux at gmail.com
https://www.linkedin.com/in/n1vux



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org