Mounting a remote directory on startup on Suse

[bomahony]

So ive got a Suse server up and running. It is connecting to a clearcase server, so i want to mount the remote filesystem as part of startup, as this is generally rebooted when im not around.

I would normally add something to /etc/init.d and put the shortcut to it in the appropriate runlevel (in this case 3). Tried that. Didnt work.

Realised the init script needed to have the LBS stuff at the start, so put that in, and used insserv to add the script. I used required-start set to $ALL

This successfully created the init script with S20, and i eneabled it with chkconfig.

So i reboot. This also didnt work. Now im getting the error:
cat /var/log/boot.msg | grep mount
mount: can't get address for tiny
Starting service automounter..done

Changed it to IP and on reboot it shows this:
mount server reported tcp not available, falling back to udp
mount: RPC: Remote system error - Network is unreachable
mount server reported tcp not available, falling back to udp
mount: RPC: Remote system error - Network is unreachable

So basically it looks like the mount is trying to happen well before the nnetwork is up.

How do i fix it?

[bomahony]

I have attached the /var/log/boot.msg

Note this is Suse running on zVM on a z10 (zlinux/s390)

However this shouldnt impact WHY this isnt working.

[bomahony]

Attachment

[gogalthorp]

I assume you have the mount setup in /etc/fstab??????

You need to set a script in a file called /etc/init.d/after.local which should contain

#! /bin/sh
mount -a

You may get more info here (not this is about samba but the problem is the same trying to mount before network is stable)

Samba: HowTo Mount a CIFS Network Share [AKA Map Network Drive] in openSUSE 11 plus FAQs

note above is an OpenSuse solution not 100% sure it would work in the Novell commercial versions

[bomahony]

i wasnt using fstab as i needed it done at a specific point in the boot sequency.

Turns out that even tough i added the LSB init, and it read $ALL, and thereby created it as an S14 item, it didnt actually run it at theis point.

Once i added $network and $remote_fs it became an S11 and was initialised at the correct point.