Am Sat, 21 Jun 2014 08:59:30 +0200 schrieb Andreas Radke <andy...@archlinux.org>:
> Am Fri, 20 Jun 2014 16:48:21 -0400 > schrieb Genes Lists <li...@sapience.com>: > > > This is probably unlikely but I'll ask. Is it possible that > > something that nfs needed (but missing from systemd service file) > > had not actually come up yet but several minutes later it was up > > and then nfs was able to start? > > > > Thought I'd ask. > > > > gene/ > > > > I'm also affected by this issue. This could be a missing > dependency /mixed up order in the nfs startup. > > -Andy This can be fixed by explicitly enabling rpcbind.service on the server. But this shouldn't be necessary because nfs-server.service has: grep rpcbind /usr/lib/systemd/system/nfs-server.service Requires= network.target proc-fs-nfsd.mount rpcbind.target After= network.target proc-fs-nfsd.mount rpcbind.target nfs-mountd.service So I assume some race condition or bug here though. -Andy
signature.asc
Description: PGP signature
