> Except perhaps for explicitly defining the location of my credentials file
> ...
> //server.name/share /smb/somefolder smbfs auto,credentials=/home/username/smbcredentials,uid=XXX,gid=XXX,umask=000 0 0
> Whereas previously they looked like:
> //server.name/share /smb/somefolder smbfs auto,credentials=smbcredentials,uid=XXX,gid=XXX,umask=000 0 0
This bug, as I have seen it, is specifically NFS related.
Your SMB fix very well might have been adding a fully qualified file name for your credentials.
I still believe it is a race between NFS and domain name resolution. In my case, it is using other servers' DNS. A background mount flag will fail, but I might try a foreground, just in case it makes a difference.
epicurea:
> Except perhaps for explicitly defining the location of my credentials file s=/home/ username/ smbcredentials, uid=XXX, gid=XXX, umask=000 0 0 s=smbcredential s,uid=XXX, gid=XXX, umask=000 0 0
> ...
> //server.name/share /smb/somefolder smbfs auto,credential
> Whereas previously they looked like:
> //server.name/share /smb/somefolder smbfs auto,credential
This bug, as I have seen it, is specifically NFS related.
Your SMB fix very well might have been adding a fully qualified file name for your credentials.
I still believe it is a race between NFS and domain name resolution. In my case, it is using other servers' DNS. A background mount flag will fail, but I might try a foreground, just in case it makes a difference.