Description of problem: Initscripts update enables network.service & network-up.service although system has switched to use NetworkManager.
This causes very long startup time.
systemctl disable network.service and systemctl disable network-up.service returns system to normal startup time.
Version-Release number of selected component (if applicable): 9.55-22
I think it's a bug that should be fixed before Mageia 6 is released.
(In reply to Sander Lepik from comment #1)
> I think it's a bug that should be fixed before Mageia 6 is released.
Well assigning it to Colin is maybe not the best way to have it fixed quickly, currently :)
Bug still present in last initscripts update: initscripts-9.55-23.mga6
Bug still present in last initscripts update: initscripts-9.55-24.mga6
Same problem in my Cauldron,not in first time
It would be good to add a note about this in the Errata, thus I'm adding the FOR_ERRATA6 keyword.
Once added to https://wiki.mageia.org/en/Mageia_6_Errata please replace FOR_ERRATA6 with IN_ERRATA6.
Still present in Mageia 6 initscripts-9.55-24.mga6.src.rpm and in Cauldron initscripts-9.55-26.mga7.src.rpm
I hope it's fixed for cauldron.
If it's fixed, I'd like to see it proposed as an update to Mageia 6, as I'm also annoyed by this bug.
Still present in Cauldron initscripts-9.78-9.mga7...
initscripts-9.55-24.mga6.src.rpm; initscripts-9.55-26.mga7.src.rpm =>
Mageia 6 =>
I'll set it as a release blocker. More and more users are probably switching to NM nowadays and update to initscripts just screws their installation :/
Found network.service and network-up.service enabled in a new Mga8 Cauldron. It is an upgrade from a clone of a Mga7 installation. Both services were disabled at origin.
initscripts-9.55-24.mga6.src.rpm; initscripts-9.78-9.mga7.src.rpm =>
initscripts-9.55-24.mga6.src.rpm; initscripts-9.78-10.mga7.src.rpm; initscripts-9.78-11.mga8.src.rpmTarget Milestone:
Mageia 7 =>
(In reply to Ulrich Beckmann from comment #12)
> Found network.service and network-up.service enabled in a new Mga8 Cauldron.
> It is an upgrade from a clone of a Mga7 installation. Both services were
> disabled at origin.
It is a systemd standard procedure to enable service,
even though you disabled it, upon new systemd release.
You have to systemctl mask unit/item_here to disable systemd from enabling
it upon new systemd release.
Should we write more about this in Mageia 7 Release notes= I only find same info in
But i think it is not general nor obvious enough?
initscripts-9.55-24.mga6.src.rpm; initscripts-9.78-10.mga7.src.rpm; initscripts-9.78-11.mga8.src.rpm =>
initscripts-9.55-24.mga6.src.rpm; initscripts-9.78-10.mga7.src.rpm; initscripts-9.78-13.mga8.src.rpm