On 10/12/21 02:03, Tim via users wrote:
On Mon, 2021-10-11 at 18:48 +0200, Markus Schönhaber wrote:
systemctl list-units --state failed
That worked anD showed that a line in fstab was in error mounting a
directory on my NAS. Hadn't tried to access that particular directory.
___
On 12/10/2021 19:08, Tim via users wrote:
On Tue, 2021-10-12 at 08:36 +0200, Markus Schönhaber wrote:
Well, if systemctl reports them as failed, there's probably a reason
to do so. My guess would be, both scripts (as "LSB:" indicates,
network.service is just a generated systemd-wrapper around th
On Tue, 2021-10-12 at 08:36 +0200, Markus Schönhaber wrote:
> Well, if systemctl reports them as failed, there's probably a reason
> to do so. My guess would be, both scripts (as "LSB:" indicates,
> network.service is just a generated systemd-wrapper around the old
> SysV init script) returned a n
12.10.21, 08:03 +0200, Tim via users:
$ systemctl list-units --state failed
UNIT LOAD ACTIVE SUBDESCRIPTION
● network.service loaded failed failed LSB: Bring up/down networking
● rc-local.service loaded failed failed /etc/rc.d/rc.local Compatibility
LOAD = Reflects wheth
On Mon, 2021-10-11 at 18:48 +0200, Markus Schönhaber wrote:
> systemctl list-units --state failed
On a whim, I looked to see what that returns for my system.
$ systemctl list-units --state failed
UNIT LOAD ACTIVE SUBDESCRIPTION
● network.service loaded failed failed LSB: Brin
11.10.21, 18:22 +0200, Robert McBroom via users:
systemctl status
●***.attlocal.net
State: degraded
Jobs: 0 queued
Failed: 1 units
Scanning the long output doesn't give any clue as to what the complaint
is about.
How can this be tracked?
systemctl list-units --state failed
systemctl status
●***.attlocal.net
State: degraded
Jobs: 0 queued
Failed: 1 units
Scanning the long output doesn't give any clue as to what the complaint
is about.
How can this be tracked?
___
users mailing list -- users@lists.fedoraproj
