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
emergency service on
On Sun, Sep 25, 2016 at 8:04 AM, Pathangi Janardhanan
wrote:
> Hi,
>
> I would like to monitor for systemd related service notifications (for
> e.g. service started, service ready, service stopped or service failed etc.)
>
> I am trying to look through the sd-bus notification, and was looking a
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:
>
> WantedBy=multi-user.target
>
> to
>
> Wa
>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 wi
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,
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 Pres
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 difference
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:
> UUID=d4a23034-8cbe-44b3-92
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
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 (
10 matches
Mail list logo
