On 2021-06-12 4:59 p.m., Ed Greshko wrote:
On 13/06/2021 07:36, Samuel Sieb wrote:
Yes, but I would think there is still a period of time associated
with calling the service, discovering the link to /dev/null
and then understanding the service has completed.
It isn't as if the service file no longer exits.
"impossible to start them" and "prohibits all kinds of activation of
the unit"
And from the description of what the "masked" status means:
Completely disabled, so that any start operation on it fails.
But as shown from the quoted log lines, "udevadm" is definitely
getting called still.
Did you miss this line? "udevadm settle" is still getting called
according to that log, so the original service file is still getting
run for some reason. From your earlier message, 542ms is still kind
of long, but not unreasonable. Do you still get the message from
udevadm in the log, though?
No, I didn't. And, yes, it is my log too.
Isn't nm-initrd.service added to the initramfs?
So that gave me the clue that led to the real problem. The service is
included in the initrd and masking it on the system doesn't change that.
Even re-creating the initrd with dracut after masking didn't change
anything.
And also the nm-initrd.service file is in dracut, so you would have to
modify it there (not the system one) to change this.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
