46 ms·
Well, since the 90's we had more than one core in the average machine. There is no reason parallel start would be problematic; I even got stuff working that ne
by ilyt 3y ago
Well, since the 90's we had more than one core in the average machine.
There is no reason parallel start would be problematic; I even got stuff working that needed network access to get creds for encrypted partition that was required for database to start and it was handled flawlessly.
More than that, if for some reason that file system wasn't mounted it would be when I told systemd to start database, it would run the service retrieving the secrets, then the mount using it, then the DB.
The worse story is with shutdown; by default most distros will cut ssh access before services are closed so if some of them hang you can't debug that remotely. But that's mostly bad settings rather than bad design of the daemon
- bandrami 3y agoI think you're definitely right that shutdown is the harder problem and it's one that init systems in general pay a lot less attention to, unfortunately. If the system has a problem coming up it often at least gets into a state where I can access it; if it hangs after being told to reboot, well... I once had to drive from Arlington VA to Seacaucus NJ to press a power button on a rack server in our datacenter, and I don't like that.
- __d 3y agoYou couldn't use the DC's remote hands?
- bandrami 3y agoIIRC the issue was if the remote hands opened our closet they would see we were over our contract limit for servers in the rack. The late 90s were kind of the wild west when it came to colos.
- __d 3y agolol, yeah, been there.
- ilyt 3y agoyou could, most modern servers also have out of band controls, but it is still PITA because you don't know whether something is wrong or it just takes extra few minutes for whatever reason