BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Debian officially forked over systemd
- Subject: [Discuss] Debian officially forked over systemd
- From: richard.pieri at gmail.com (Richard Pieri)
- Date: Sat, 29 Nov 2014 21:02:03 -0500
- In-reply-to: <BN3PR0401MB120445DF33505CF00597D8F7DC7C0@BN3PR0401MB1204.namprd04.prod.outlook.com>
- References: <5479FEA1.5000504@gmail.com> <547A062F.8080906@horne.net> <BN3PR0401MB120445DF33505CF00597D8F7DC7C0@BN3PR0401MB1204.namprd04.prod.outlook.com>
On 11/29/2014 7:50 PM, Edward Ned Harvey (blu) wrote: > The arguments about preventing downtime are bunk, unless somebody > shows that systemd causes downtime. Which it doesn't. Last major update to my home box, systemd broke Samba. No changes were made to the Samba configuration; systemd simply refused to start the daemons and refused to tell me why. They started correctly when I started them manually. They started correctly after I removed systemd and its dependencies and installed sysvinit. So yes, systemd can cause, and has caused, downtime for me. -- Rich P.
- References:
- [Discuss] Debian officially forked over systemd
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] Debian officially forked over systemd
- From: bill at horne.net (Bill Horne)
- [Discuss] Debian officially forked over systemd
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] Debian officially forked over systemd
- Prev by Date: [Discuss] Debian officially forked over systemd
- Next by Date: [Discuss] Debian officially forked over systemd
- Previous by thread: [Discuss] Debian officially forked over systemd
- Next by thread: [Discuss] Debian officially forked over systemd
- Index(es):