Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc Subject: Re: Wonderful Windows Zaps Banks/Transport/Media after "Update" Yesterday Date: 22 Jul 2024 05:31:36 GMT Lines: 22 Message-ID: References: <87h6cl74ix.fsf@tilde.institute> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net fkVcdR409vV+f6mEDaShswwbEBJOeXAn2HplAs4yfWVwO/7i8g Cancel-Lock: sha1:VZV/XGKh7EaOaq06OQ7LNaSM3eg= sha256:O0OgbD5U2kDiPH3X2a7cSQJ3an3yt3fEaVyjBK1SYyo= User-Agent: Pan/0.149 (Bellevue; 4c157ba) Xref: csiph.com comp.os.linux.misc:57125 On Sun, 21 Jul 2024 22:04:11 GMT, Charlie Gibbs wrote: > Note: not all outages are due to software bugs on our part. > Configuration changes on the customer site can kill things just as > effectively, and in fact are the more likely cause of a failure. Or > maybe someone unplugged something they shouldn't. But if data stops > flowing, the finger is pointed at us first, rightly or wrongly. So not > only do we not do updates on Friday, we recommend the philosophy on > genreral principles. Yup. Our clients are PSAPs (dispatch software in 911 call centers). They get really unhappy when the software goes down during a mass casualty incident. The typical procedure is to deploy software to a backup/training server and test it using the site's configuration files before pushing it to the main servers and workstations. We're definitely #1 on the 'who do you call?' list. My favorite goes back to the days of modems. Paging suddenly stopped working and it took a while to figure out a dispatcher got sick of listening to the modem and turned it off.