I'm trying to mount an NFS share on boot. I put the correct parameters into my fstab file. It mounts perfect when I issue "mount -a". But, it does not mount on boot. The network is not ready yet at the time it tries, so it fails. Log file says this:
It doesn't seem like Atomic Host is using standard automount because I don't have that service. It's just unique enough that I can't figure out exactly what to do about this. How do I get my mount to wait until my network is up and connected?Sep 19 10:16:42 judge.hardman.local systemd[1]: Reached target Remote File Systems (Pre).
Sep 19 10:16:42 judge.hardman.local systemd[1]: Starting Remote File Systems (Pre).
Sep 19 10:16:42 judge.hardman.local systemd[1]: Mounting /mnt/rivera/files...
Sep 19 10:16:42 judge.hardman.local systemd[1]: Starting Availability of block devices...
Sep 19 10:16:42 judge.hardman.local systemd[1]: Started Notify NFS peers of a restart.
Sep 19 10:16:42 judge.hardman.local systemd[1]: Started Enable periodic update of entitlement certificates..
Sep 19 10:16:42 judge.hardman.local systemd[1]: Started Availability of block devices.
Sep 19 10:16:42 judge.hardman.local mount[950]: mount.nfs: Failed to resolve server rivera: Name or service not known
Sep 19 10:16:42 judge.hardman.local mount[950]: mount.nfs: Operation already in progress
Sep 19 10:16:42 judge.hardman.local systemd[1]: mnt-rivera-files.mount mount process exited, code=exited status=32
Sep 19 10:16:42 judge.hardman.local systemd[1]: Failed to mount /mnt/rivera/files.
Sep 19 10:16:42 judge.hardman.local systemd[1]: Dependency failed for Remote File Systems.
Sep 19 10:16:42 judge.hardman.local systemd[1]: Job remote-fs.target/start failed with result 'dependency'.
Sep 19 10:16:42 judge.hardman.local systemd[1]: Unit mnt-rivera-files.mount entered failed state.