Description of problem:
Currently rpc-statd-notify.service requires network-online.target. This means that installing nfs-utils, which enables nfs-client.target, which depends on rpc-statd-notify.service, results in you waiting for the network to come online. You may have installed nfs-utils just to mount something one time or for autofs such as myself. Because of the forking change made to the rpc-statd-notify.service service I think we can make this depend on network.target instead. It should wait in the background for up to 15 min to try and notify servers. This saved 10 seconds off my boot by simply changing this dependency. There could of course be a flaw in my logic :-)
Version-Release number of selected component (if applicable):
Since bug 1181708 has been fixed this should now be possible I think.
Any comment on this idea? Does it sound like a good solution or not?
(In reply to Eric Work from comment #1)
> Any comment on this idea? Does it sound like a good solution or not?
I did take a look at this... it seems in network-online.target there
is an After=network.target which mean network.target will be
started first so I still think there will be a delay...
have you tested it out?
From my observations network.target only requires that the interfaces are up as opposed to connected to the network with an IP with network-online.target. In my case I don't have any NFS notifications to be sent so I can't say what would happen with just network.target if that was the case. My assumption was that it would try to 15 minutes which by then the interface should have an IP. Making this change does save a lot of time on my system which boots pretty quick due to a BIOS with a fast boot mode and SSDs.
nfs-utils-1.3.1-6.1.fc21 has been submitted as an update for Fedora 21.
It looks like both "Requires" and "After" need to be changed to "network.target" in order to get the benefit. I have the following lines locally.
This cuts my boot time from the big red button push to 21 sec instead of the original 31 sec because the login prompt is not waiting for the internet to come up. Only changing "After" didn't have any effect unfortunately.
nfs-utils-1.3.1-6.1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
The two upstream commits
Can you please push new release to f22 at bodhi ?
nfs-utils-1.3.1-6.2.fc21 has been submitted as an update for Fedora 21.
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing nfs-utils-1.3.1-6.2.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Is there a reason why you don't push any update to f22 at bodhi?
Sorry, i have removed nfs-utils from mate livecd spin to avoid a slow boot, until you update f22.
(In reply to Wolfgang Ulbrich from comment #12)
> Is there a reason why you don't push any update to f22 at bodhi?
> Sorry, i have removed nfs-utils from mate livecd spin to avoid a slow boot,
> until you update f22.
Sorry.. at this point I didn't think I needed to... Will do!
nfs-utils-1.3.2-2.0.fc22 has been submitted as an update for Fedora 22.
the issue still exists with nfs-utils-1.3.2-0.2.fc22 from f22 stable, tested with a local build livecd, today.
Confirmed that nfs-utils-1.3.2-2.0.fc22 fix the issue with mate-compiz live spin.
NetworkManager-wait-online.service doesn't start anymore.
nfs-utils-1.3.2-2.0.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
nfs-utils-1.3.1-6.2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.