Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Am 01.12.2016 um 02:36 schrieb Manuel Amador (Rudd-O): On 09/26/2016 10:31 AM, Reindl Harald wrote: Am 26.09.2016 um 11:27 schrieb Oliver Neukum: On Sun, 2016-09-25 at 23:57 +0200, Reindl Harald wrote: RTFM - when you don't say "nofail" it's ecpected to be crucial your entry says it's

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On 09/26/2016 10:31 AM, Reindl Harald wrote: > > > Am 26.09.2016 um 11:27 schrieb Oliver Neukum: >> On Sun, 2016-09-25 at 23:57 +0200, Reindl Harald wrote: >>> >>> RTFM - when you don't say "nofail" it's ecpected to be crucial >>> >>> your entry says it's crucial >> >> That in turn raises the

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Am 27.11.2016 um 19:23 schrieb Jonathan de Boyne Pollard: Lennart Poettering: "nofail" has been around as long as fstab has been around really. This is a falsehood. /etc/fstab has a history that goes back to the 20th century. It was in UNIX System 5 Release 3, 4.2BSD, and OSF/1, for

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Lennart Poettering: "nofail" has been around as long as fstab has been around really. This is a falsehood. /etc/fstab has a history that goes back to the 20th century. It was in UNIX System 5 Release 3, 4.2BSD, and OSF/1, for examples. In contrast, the "nofail" option was invented in

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Sun, 06.11.16 11:41, Reindl Harald (h.rei...@thelounge.net) wrote: > > You mix two different things. > > > > 1. The behavior that if filesystem from /etc/fstab fails to mount, boot > > is stopped and administrator intervention is required existed long > > before systemd. > > > > 2. Password

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Sun, Nov 06, 2016 at 09:28:59AM +0300, Andrei Borzenkov wrote: > 1. The behavior that if filesystem from /etc/fstab fails to mount, boot > is stopped and administrator intervention is required existed long > before systemd. I have never seen this. > 2. Password is requested not by systemd,

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

06.11.2016 13:41, Reindl Harald пишет: > > the current behavior is correct but "machine stops booting and require > password" in fact is "new" on systemd driven machines > It may be new for this or that distribution. It is certainly not new in general. echo "fsck failed for

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Fri, 04.11.16 16:14, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > On Thu, Nov 03, 2016 at 10:55:35PM +0100, Lennart Poettering wrote: > > On Mon, 26.09.16 07:02, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > > > On Mon, Sep 26, 2016 at 10:52:50AM +1300, Sergei Franco wrote: > > >

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Mon, 26.09.16 07:02, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > On Mon, Sep 26, 2016 at 10:52:50AM +1300, Sergei Franco wrote: > > The emergency mode assumes console access, which requires physical access, > > which is quiet difficult if the machine is remote. > > It does also assume

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Sun, Sep 25, 2016 at 08:09:20PM -0400, Dave Reisner wrote: > Making bootup potentially interactive in this manner is strictly worse > than dumping you into emergency mode. At least with emergency mode, you > might be able to add dependencies to emergency.target such that, for > example, an sshd

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Mon, Sep 26, 2016 at 10:52:50AM +1300, Sergei Franco wrote: > The emergency mode assumes console access, which requires physical access, > which is quiet difficult if the machine is remote. It does also assume knowledge of the root password, which is in enterprise environments not often the

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Mon, Sep 26, 2016 at 12:31:10PM +0200, Reindl Harald wrote: > because earlier systems (sysvinit) hat no concept like emergency mode as > they where a lousy bunch of scripts where you ended in case of a crucial > disk failing in a undefined state? > > because earlier systems had no concept for

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

26.09.2016 17:58, Xen пишет: > Andrei Borzenkov schreef op 26-09-2016 15:28: > >> What effect do you expect? If service Requires mount point and mount >> point is not available, service startup fails. That is correct and >> expected behavior. If service does not require mount point, service >>

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Andrei Borzenkov schreef op 26-09-2016 15:28: What effect do you expect? If service Requires mount point and mount point is not available, service startup fails. That is correct and expected behavior. If service does not require mount point, service should be saying Wants and After. Which is at

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Mon, Sep 26, 2016 at 4:20 PM, Xen wrote: ... >> >> because earlier systems (sysvinit) hat no concept like emergency mode >> as they where a lousy bunch of scripts where you ended in case of a >> crucial disk failing in a undefined state? >> >> because earlier systems had no

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Reindl Harald schreef op 26-09-2016 12:31: Am 26.09.2016 um 11:27 schrieb Oliver Neukum: On Sun, 2016-09-25 at 23:57 +0200, Reindl Harald wrote: Am 25.09.2016 um 23:52 schrieb Sergei Franco: I am looking at correct way to disable the "feature" of emergency mode when systemd encounters

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Am 26.09.2016 um 11:27 schrieb Oliver Neukum: On Sun, 2016-09-25 at 23:57 +0200, Reindl Harald wrote: Am 25.09.2016 um 23:52 schrieb Sergei Franco: I am looking at correct way to disable the "feature" of emergency mode when systemd encounters missing block device entires in fstab. For

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Mon, Sep 26, 2016 at 12:27 PM, Oliver Neukum wrote: > On Sun, 2016-09-25 at 23:57 +0200, Reindl Harald wrote: >> >> Am 25.09.2016 um 23:52 schrieb Sergei Franco: >> > I am looking at correct way to disable the "feature" of emergency mode >> > when systemd encounters missing

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Sun, 2016-09-25 at 23:57 +0200, Reindl Harald wrote: > > Am 25.09.2016 um 23:52 schrieb Sergei Franco: > > I am looking at correct way to disable the "feature" of emergency mode > > when systemd encounters missing block device entires in fstab. > > > > For example: > > > > the following entry

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Mon, Sep 26, 2016 at 8:11 AM, Mantas Mikulėnas wrote: > That said, I suspect the reason it's not done by default is that it also > needs *networking*, and every distro has its own network setup services, It also needs logind unless you prepare special PAM configuration for

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Mon, Sep 26, 2016 at 4:00 AM, Sergei Franco wrote: > From further reading of documentation, please correct me if I am wrong, > one way (not sure if correct) to start SSH during emergency mode is to edit > /etc/systemd/system/sshd.service and modify: > >

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

>From further reading of documentation, please correct me if I am wrong, one way (not sure if correct) to start SSH during emergency mode is to edit /etc/systemd/system/sshd.service and modify: WantedBy=multi-user.target to WantedBy=multi-user.target emergency.target Do I need to do anything

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

I wasn't aware of emergency.target existence (systemd is new to me). What would be correct way to automatically start networking/ssh in emergency mode? The only thing I could find is this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1213781 Sergei. On 26 September 2016 at 13:09,

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Mon, Sep 26, 2016 at 11:35:51AM +1300, Sergei Franco wrote: > Thank you for your quick reply. > > I just tested this scenario on Ubuntu 12.04LTS (with upstart) and it > present the following message: > > The disk drive for /data is not ready yet or not present. > keys:Continue to wait, or

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Thank you for your quick reply. I just tested this scenario on Ubuntu 12.04LTS (with upstart) and it present the following message: The disk drive for /data is not ready yet or not present. keys:Continue to wait, or Press S to skip mounting or M for manual recovery So it is not as big

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

On Mon, Sep 26, 2016 at 10:52:50AM +1300, Sergei Franco wrote: > Hi, > > I am looking at correct way to disable the "feature" of emergency mode when > systemd encounters missing block device entires in fstab. > > For example: > > the following entry is in /etc/fstab: >

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Am 25.09.2016 um 23:52 schrieb Sergei Franco: I am looking at correct way to disable the "feature" of emergency mode when systemd encounters missing block device entires in fstab. For example: the following entry is in /etc/fstab: UUID=d4a23034-8cbe-44b3-92a5-3d38e1816eff /data

[systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

Hi, I am looking at correct way to disable the "feature" of emergency mode when systemd encounters missing block device entires in fstab. For example: the following entry is in /etc/fstab: UUID=d4a23034-8cbe-44b3-92a5-3d38e1816eff /data xfs defaults0 0 If the drive