I have searched in this forum, the man pages, SuSE documentation, and elsewhere, but have not found a definitive answer to my question.
I have a laptop which may not always be connected to the NFS network where an fstab-listed share resides. In the past, I have had a PC fail to boot because an external drive listed in fstab was not available.
One of the fstab options mentioned is nofail. And I have seen references to others.
For NFS mounts on my laptop, I use “autofs”. That way the share is not mounted until needed, and booting does not fail. If I’m away from home, as long as I don’t attempt to actually access that share, I won’t run into any problems.
Thanks again for the advice. I’ve now implemented autofs on two machines. Since the shares are identical, I only needed to copy the auto.master and auto.[misc] files to the second platform. And I may opt for this arrangement in the other machines using fstab to mount the share.
I’m in a single-server environment, with only one share at the moment (i.e., a single map file). Would an indirect configuration provide any benefits in my case?
Thanks. Based on my brief review of the site I mentioned above and others, I suspect it might have an impact in a large scale computing environment with multiple servers - not my situation at all. More importantly, it’s working here and working well.
The writer on another website expressed preference for autofs over fstab for network shares (as opposed to internal shares). Although I’ve become reasonably proficient in editing fstab, I can see the advantages of autofs - it’s an elegant solution to share mounts.
Thank you for bringing it to my attention - I was not previously familiar with the utility.