SlackwareThis Forum is for the discussion of Slackware Linux.
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.
All right, I have a 3 Samba shares on my Slack server that I connect to from my Slack desktop. I have edited fstab so that they will connect during boot time. What I have noticed during boot time on Slack desktop is that sometimes eth0 doesn't come up in time for it to connect to all 3 shares. Sometimes during boot it will connect to all 3, and the rest of the time just 2 of them while I have to manually mount the 3rd (when eth0 doesn't come up in time). I figure it's this just b/c configuration is right AND my switch LED (a Cisco one) for that port remains amber right up to that point basically. So is there anyway I could buy a few extra seconds during boot time so that all shares will connect all the time?
Distribution: Slackware 11.0; Kubuntu 6.06; OpenBSD 4.0; OS X 10.4.10
You could perhaps change fstab so that those shares don't automatically mount and then put mount commands in your rc.local. You'd still get them mounted during boot pretty much automatically. By the time rc.local is run, your network should be up.
Rather than create a new thread I'll keep this one going. I have ran into a new obstacle that should be a quick fix...and I have done my part to try and fix it with no luck.
The drives get mounted fine using the rc.local script BUT it completely screws up the permissions for the root directory of that directory. So basically it goes like this...
Say this is the directory...
/MP3 ......after the mounting, it assigns root as the owner of that directory.
But any subdirectory of that directory has the correct normal user non-root permissions.
Now, I have tried just adding the chown option to those directories (to the user who should own the files) in the rc.local file but it tells me that that option cannot be permitted. Even manually doing it will not work. I am guessing what is happening is when the rc.local file gets processed, since it is owned by root, it automatically places root as the owner of that directory it is mounting. This is really a pain just b/c I do create directories in the main directory and it tells me access is denied.
I have thought what I could do is create a mount command script under the actual users home directory and have rc.local call it. Would that work? I am not too sure if I need any more options in the mount command just b/c fstab covers a lot of the permissions options as is.
It would still be run as root and thus, commands would be executed as root. You might be able to add -o user=USERID to the mount command to get it mounted as that user. There are also smb-specific options you may want to explore. See smbmount(8).