Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If the server is off obviously I don't want to access it, I'd like that this state don't affect the system (boot process and nemo), do I need other params in fstab?
I have not investigated if using _netdev would automatically try to mount the share regardless of the noauto option. You can run the systemd-analyze blame command to see what is causing the specific slowness when the server is off.
In addition if you have a bookmark for that share I believe when nemo starts it will automatically try to access that share which will fail since the server is off.
I have remove "_netdev" param, and I reboot, first time It works!! no problem with nemo folder client and I haven't to wait 90 seconds to start, but second, third.... times it doesn't work well. Sometimes it works and other it doesn't work
The sometimes "systemctl" shows the "xxx.mount" and "xxx.automount" services failed, great!! it works, but the other times systemctl shows "xxx.mount" failed and "xxx.automount" waiting
Just throwing this out as an idea. Have you tried background-mounting? I.e. adding the bg and perhaps the retry mount options. Not sure if this interferes with systemd or if it is advisable in fstab.
EDIT: The systemd.mount man page mentions bg, but I don't have enough time to grasp the meaning.
Last edited by berndbausch; 12-09-2018 at 08:06 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.