Am 08.02.21 um 18:27 schrieb Lennart Poettering:
Masking is a last resort thing, you really want to use that only after
having investigated everything. You use it here anyway to mask out a
really low-level system thing, hence you might get warnings about
this.
You can of course mask sys-fs-fuse-connections.mount too
no, you can't at least on F33
"systemctl mask sys-fs-fuse-connections.mount" only works on F32 at the
moment, on F33 "sys-module-fuse.device" is masked but at the same moment
"active (plugged)" and cries for "sys-fs-fuse-connections.mount"
fuse kernel module is loaded on a bare install after reboot - please get
your facts straight, i already tried to mask them last year *before*
writing the ignored bug report at the fedora bugzilla
[root@rawhide ~]# system-errors.sh
Feb 8 19:17:01 rawhide systemd[1]: sys-module-fuse.device: Failed to
enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount
is masked.
[root@rawhide ~]# systemctl status sys-module-fuse.device
sys-fs-fuse-connections.mount
● sys-module-fuse.device - /sys/module/fuse
Loaded: masked (Reason: Unit sys-module-fuse.device is masked.)
Active: active (plugged) since Mon 2021-02-08 19:17:00 CET; 5min ago
Device: /sys/module/fuse
Feb 08 19:17:01 rawhide.vmware.local systemd[1]: sys-module-fuse.device:
Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit
sys-fs-fuse-connections.mount is masked.
● sys-fs-fuse-connections.mount
Loaded: masked (Reason: Unit sys-fs-fuse-connections.mount is masked.)
Active: inactive (dead)
[root@rawhide ~]#
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
