On 27/10/18 6:15 pm, Ed Greshko wrote:
On 10/27/18 2:46 PM, Stephen Morris wrote:
My main concern with this is not the mounts failing at boot, I can understand why they
failed, but more why the networkmanager wait online process is failing. I tried a boot
with the ethernet cable disconnected from the pc, but that made no difference.
Could vpn definitions be impacting the process? I have a number of vpn definitions,
which are not getting started as I require, but all of them have the option
'Automatically connect to this network when it is available' ticked, and both
networmanager and 'kde settings->network->connections' do not let me switch it off.
Oh, if you're wanting to mounts to work properly at boot time with only NetworkManager
WaitOline then I, for one, am unable to offer any help.
I don't have any complicated network setup and no matter what I tried the NFS mounts
didn't consistently work no matter what I tried. So, that is why I went the rc.local
route at first and then switched to auto-fs mounts.
Sorry Ed, just one more question around this. You mentioned in an
earlier thread that you had the auto-mount process working on a CIFS
partition. How did you get it to work, I can't get it to. Both 'LS
/MNT/NAS' and 'SUDO LS /MNT/NAS' fail to mount the partition. I don't
understand why the second command didn't work, as with CIFS only
supporting mounting by Root, the sudo function should have worked.
regards,
Steve
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
