"Refresh" smb mounts

hi there,

I have something weird happening here:
I have a samba server in my network sharing two directories, media & data.
On my workstation i have themn mounted with the fstab like
//192.168.0.2/data /mnt/data cifs users,auto,uid=1000,gid=1000 0 0
and it seems to work just fine EXCEPT:
Some folders that I copy on the shared drives do not show up when reading the directory with Dolphin or Konqueror - they don’t even show-up in the console - they’re like “not availabale” unless i type the correct path into the address bar and hit enter, then i get there and i also see the ‘missing’ directories when looking e.g like “smb://server/media/Albums/” at the directory (in Konqueror).
Isn’t this weird? Do I miss some kind of refreshing flag in my fstab mount or what could cause this behaviour? I may need to mention that every file written on the samba sharte gets assigned permission 0777.

Thanks for your help and hints!
Ron:confused:

Do you mean GID=100?

Yes, I changed this and now it seems to list the whole direcory content when the share is mounted BUT - I changed this in /etc/fstab and the share doesn’t get mounted on bootup but once the system is booted i make a sudo mount -a and this mounts the shares just fine. Why doesn’t it mount them on bootup anymore?

Thanks,
Ron

fstab lines:
//192.168.0.2/media /mnt/media cifs users,auto,uid=1000,gid=100 0 0
//192.168.0.2/data /mnt/data cifs users,auto,uid=1000,gid=100 0 0

Try adding this in the options: _netdev
That instructs to wait for the network to get up before executing that mount – worth a try. There’s another option if that fails, but let’s see first.

:frowning: egative, that did not help :slight_smile: Still had to do a “sudo mount -a” after booting up :frowning:
Thanks for your help! :o

OK, try the “smack in the mouth” approach. Open the file “boot.local” from the location /etc/init.d/boot.local and put this line in the bottom of it:
mount -a

That might get a result. There’s one final method if that fails (the smack over the head method :eek: ).

Ah alright - sure that’s a good hint :wink: … but there’s no /etc/init.d/boot.local :o should i create it - would opensuse still execute it at the en of the booting process or should i rather create an S99MountA link in rc5.d? - or would this have been your last suggestion? :wink:

I’m really surprised it’s not there. Are you sure? It’s got an icon like a TV screen, but it’s really a text file. Here are the default contents if you need to create it (but it only needs the first line):

#! /bin/sh

Copyright (c) 2002 SuSE Linux AG Nuernberg, Germany. All rights reserved.

Author: Werner Fink <werner@suse.de>, 1996

Burchard Steinbild, 1996

/etc/init.d/boot.local

script with local commands to be executed from init on system startup

Here you should add things, that should happen directly after booting

before we’re going to the first run level.

Or go with your alternate solution (which I only dimly understand) if that suits you.

well i’m using the shell and /etc/init.d/boot.local doesn’t exist:
ls -l /etc/init.d/boot.local
I’ll create one and try it this way.

Thanks!

Okay now,

I guess my setup requires a little more tweaking:
This is what I have:
boot.local


                echo Setting up VirtualBox depencies [start]
                /etc/init.d/vboxdrv setup
                modprobe vboxdrv
                VBoxAddIF vbox0 reg br0
                echo Setting up VirtualBox depencies [end]
                echo mount drives
                mount -a
reg@desktop:~>


I first have rto setup my virtual box interfaces and it takes apparently a couple of seconds for the br0 to get an IP address that’s why I see “network unreachable”. If I did the “mount -a” before the vbox setup it wouldn’t work since eth0 is configured to have 0.0.0.0 with no bridge.
What can I do here :frowning:

What i forgot to mention is: I had the vbox commands in /etc/init.d/network and I still only saw “network unreachable” when executing “mount -a” from boot.local

I’ve not used Virtual Box. – newbie there. Despite that, suppose you think it takes 5 (or whatever) seconds to get settled and ready to accept the command mount -a. Make a root crontab entry to instruct to run the command 5 (or whatever) seconds after boot. This command (su to root first) will open the cron editor:
crontab -e
Then put this line in there:
@reboot sleep 5;mount -a
adjust the 5 for whatever delay you want.