[systemd-devel] Antw: [EXT] Re: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit modprobe at fuse.service is masked

[Ulrich Windl]

>>> Reindl Harald <h.reindl at thelounge.net> schrieb am 08.02.2021 um 19:01 in
Nachricht <e269c7e2-7597-1f49-d827-7117363c423f at thelounge.net>:

> 
> Am 08.02.21 um 18:27 schrieb Lennart Poettering:
>> On So, 07.02.21 22:43, Reindl Harald (h.reindl at thelounge.net) wrote:
>> 
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1909805 
>> 
>> In response to your actual issue, ignoring all the nasty wording:
>> 
>> 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
> who needs anything related to fuse at every boot?
> fuse is nothing in common used
> fuse is not used unconditional
> 
> directly after boot on a server‑vm with no fuse business
> 
> [root at testserver:~]$ lsmod | grep fuse
> fuse                  163840  1

First it seems you fuse module is used by another module, and then in SLES15
SP2 with libvirt and two running Xen PVMs, I see no fuse being used or even
loaded. So maybe find out who requests fuse...

> 
> my only usecase on 50 machines is every few weeks fuse.sshfs abd what 
> makes people nasty is that for months nobody responds to systemd related 
> issues in the Fedora bugracker
> 
> if something is usiong fuse it happily loads the kernel module on‑demand 
> for years
> 
> 
> 
> 
> _______________________________________________
> systemd‑devel mailing list
> systemd‑devel at lists.freedesktop.org 
> https://lists.freedesktop.org/mailman/listinfo/systemd‑devel