Systemd and nfs-common ?

Question

My nfs-client setup takes 62s to mount a nfsv4 share. I've tried to solve this by creating an own systemd nfs-common.service but it fails. It doesn't see rpcbind as started, which it is. I've googled high and low for a systemd *.service that works but haven't any nfs-common.service file at all.
I have ExecStart=/etc/rc.d/nfs-common start in my .service file and it is enabled but status message is;
nfs-common.service - nfs-common
Loaded: loaded (/etc/systemd/system/nfs-common.service; enabled)
Active: failed (Result: exit-code) since Sat, 19 May 2012 12:25:43 +0200; 10min ago
Process: 1911 ExecStart=/etc/rc.d/nfs-common start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/nfs-common.service
sudo /etc/rc.d/nfs-common start gives;
Start rpcbind first. [FAIL]
Same as in journal systemd-journalctl | grep -i nfs;
May 19 12:14:09 mediadatorn kernel: RPC: Registered tcp NFSv4.1 backchannel...e.
May 19 12:14:09 mediadatorn kernel: FS-Cache: Netfs 'nfs' registered for caching
May 19 12:14:10 mediadatorn[103]: Inserted module 'nfs'
May 19 12:14:11 mediadatorn nfs-common[227]: Start rpcbind first. [FAIL]
All this came about since I started trying to optimize systemd. Before today, when I tried to disable all legacy arch units, I had the nfs client running ok. I did this after reading falconindys tip in the big systemd thread. By the way, that thread is so big it has become nearly useless.
Boot up times:
systemd-analyze
Startup finished in 13269ms (kernel) + 94810ms (userspace) = 108080ms
systemd-analyze blame
62034ms mnt-SERVER_NYTT.mount
6764ms console-kit-daemon.service
2787ms systemd-modules-load.service
1838ms home.mount
867ms syslog-ng.service
552ms rpc-statd.service

Answer 1

swanson wrote:
I followed this
falconindy wrote:
arch-daemons.target. Sadly, it's going to be a little longer than I wanted until that unit disappears. That said, the intended usage of that target was never meant to be more than:
1) Install systemd, initscripts-systemd, systemd-arch-units (arch-daemons.target is enabled)
2) reboot
3) copy /run/systemd/generator/arch-daemons.target.wants/*.service to /etc/systemd/system for anything where a native unit file doesn't exist
4) kill -1 1 (refreshes systemd's unit database)
5) systemctl enable *.service (for the services you copied over in step 3)
6) disable arch-daemons.target
7) ????
8) profit.
(finally found it)
Right now I'm trying to reverse it and start over.
I tried this, and immediately didn't get it to mount.  I restarted rpcbind (supposedly already running) and nfs-common and I think it still stalled on mounting, but now I that I've been away from it, it finally did mount.
Last edited by nomorewindows (2012-06-24 00:09:47)