Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43955 - [systemd] Could provide a warning because local-fs.target has OnFailure=emergency.target
Attached to Project:
Arch Linux
Opened by James (thx1138) - Thursday, 26 February 2015, 02:54 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 14 March 2015, 15:30 GMT
Opened by James (thx1138) - Thursday, 26 February 2015, 02:54 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 14 March 2015, 15:30 GMT
|
Detailssystemd 219-2
In /usr/lib/systemd/system/local-fs.target there is: OnFailure=emergency.target OnFailureJobMode=replace-irreversibly If there is any entry in /etc/fstab that should auto-mount and fails to mount, then systemd will shut down an otherwise functional system. That seems a bit severe, but maybe not unreasonable. I had an old usbfs entry in fstab: usbfs/proc/bus/usb usbfs defaults,user,noauto 0 0 |
This task depends upon
Closed by Dave Reisner (falconindy)
Saturday, 14 March 2015, 15:30 GMT
Reason for closing: Upstream
Additional comments about closing: Not a packaging bug. If you have concerns about systemd behavior here, bring it up with upstream.
Saturday, 14 March 2015, 15:30 GMT
Reason for closing: Upstream
Additional comments about closing: Not a packaging bug. If you have concerns about systemd behavior here, bring it up with upstream.
I had an old usbfs entry in fstab:
usbfs /proc/bus/usb usbfs defaults,user 0 0
which apparently will fail to mount on the 3.19 kernel. Without "noauto", systemd will then run emergency.target and shut down the system. Any other problematic entry in /etc/fstab will produce the same result.
I'm thinking that an install note, warning about faulty entries in fstab, might be appropriate for this systemd 219 upgrade.