I have just upgraded to suse 9. My machine is set up as an NIS client. But it wont moount any home directories. Actually this isnt strictly true. In order to actually make it an NIS client in the first place I had to add a line to /etc/fstab to mount the home direcories, which looks like this: homer:/home /home nfs rw 0 0 But when the machine boots, this line appears to be ignored. If I go to command line and type mount -a it reruns fstab and mount everything fine. My question is why doest this happen at boot up? Am I missing something this line that would stop it mounting at boot time? I have had a look through the suse manual but it doest list many examples of options that can be used in fstab. All of them seem quite irrelavent for what I need to do. But also had a search on the net but couldnt Find anything of any help. Has anyone else had this problem? Any advice pionters would be much appeciated. Cheers -- Andrew Nix St Pauls Catholic High School Firbank Road Newall Green Wythenshawe Manchester M23 2YS tel: 0161 4922040 fax: 0161 4982030
--- Andrew Nix
I have just upgraded to suse 9. My machine is set up as an NIS client. But it wont moount any home directories. Actually this isnt strictly true.
In order to actually make it an NIS client in the first place I had to add a line to /etc/fstab to mount the home direcories, which looks like this:
homer:/home /home nfs rw 0 0
That line looks valid, assuming "homer" is a valid HOST name that your computer knows about.
But when the machine boots, this line appears to be ignored. If I go to command line and type mount -a it reruns fstab and mount everything fine.
:) I know why that is (see below).
My question is why doest this happen at boot up? Am I missing something this line that would stop it mounting at boot time?
You have to ensure that the NFS Server is running (hint, tweak the variable in /etc/rc.config), that way it runs before the drives are mounted. HTH, Thomas Adam ===== Thomas Adam "The Linux Weekend Mechanic" -- www.linuxgazette.com ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk
Thomas Adam said:
--- Andrew Nix
wrote: I have just upgraded to suse 9. My machine is set up as an NIS client. But it wont moount any home directories. Actually this isnt strictly true.
In order to actually make it an NIS client in the first place I had to add a line to /etc/fstab to mount the home direcories, which looks like this:
homer:/home /home nfs rw 0 0
That line looks valid, assuming "homer" is a valid HOST name that your computer knows about.
It is valid and it does know about it.
But when the machine boots, this line appears to be ignored. If I go to command line and type mount -a it reruns fstab and mount everything fine.
:) I know why that is (see below).
My question is why doest this happen at boot up? Am I missing something this line that would stop it mounting at boot time?
You have to ensure that the NFS Server is running (hint, tweak the variable in /etc/rc.config), that way it runs before the drives are mounted.
Im confused. The NFS server on homer? What will I have to tweak in rc.config? -- Andrew Nix St Pauls Catholic High School Firbank Road Newall Green Wythenshawe Manchester M23 2YS tel: 0161 4922040 fax: 0161 4982030
--- Andrew Nix
Im confused. The NFS server on homer? What will I have to tweak in rc.config?
Right... I can't remember how SuSE does it, but... On Homer do: 1. Edit /etc/rc.config search for "NFS" and ensure that it loads the NFSSERVER script (probably named: /etc/init.d/nfsserver. having done that, as root, run: # SuSEConfig 2. On the client you wish to mount from NFS, ensure that the NFS client is running (hint, again, check: /etc/rc.config for this_, and do: # SuSEConfig (as root, if you make any changes to the /etc/rc.config file). Then, when you've done that, on both machines do: telinit n where "n" is the number of your default run-level. If you boot into a graphical display n == 5. If not then n == 3 (most likely). HTH, -- Thomas Adam ===== Thomas Adam "The Linux Weekend Mechanic" -- www.linuxgazette.com ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk
On Thu, Oct 30, 2003 at 02:45:38PM -0000, Andrew Nix wrote:
I have just upgraded to suse 9. My machine is set up as an NIS client. But it wont moount any home directories. Actually this isnt strictly true. In order to actually make it an NIS client in the first place I had to add a line to /etc/fstab to mount the home direcories, which looks like this:
homer:/home /home nfs rw 0 0
But when the machine boots, this line appears to be ignored. If I go to command line and type mount -a it reruns fstab and mount everything fine. My question is why doest this happen at boot up? Am I missing something this line that would stop it mounting at boot time?
The usual approach is to mount all non network filesystems at the start of the boot process. With mounting of network filesystems being done later. i.e. after configuration of the network.
I have had a look through the suse manual but it doest list many examples of options that can be used in fstab. All of them seem quite irrelavent for what I need to do. But also had a search on the net but couldnt Find anything of any help.
IIRC SuSE performs the latter by running a script called "nfs", check this is actually being run. -- Mark Evans St. Peter's CofE High School Phone: +44 1392 204764 X109 Fax: +44 1392 204763
Mark Evans said:
On Thu, Oct 30, 2003 at 02:45:38PM -0000, Andrew Nix wrote:
I have just upgraded to suse 9. My machine is set up as an NIS client. But it wont moount any home directories. Actually this isnt strictly true. In order to actually make it an NIS client in the first place I had to add a line to /etc/fstab to mount the home direcories, which looks like this:
homer:/home /home nfs rw 0 0
But when the machine boots, this line appears to be ignored. If I go to command line and type mount -a it reruns fstab and mount everything fine. My question is why doest this happen at boot up? Am I missing something this line that would stop it mounting at boot time?
The usual approach is to mount all non network filesystems at the start of the boot process. With mounting of network filesystems being done later. i.e. after configuration of the network.
I have had a look through the suse manual but it doest list many examples of options that can be used in fstab. All of them seem quite irrelavent for what I need to do. But also had a search on the net but couldnt Find anything of any help.
IIRC SuSE performs the latter by running a script called "nfs", check this is actually being run.
Sorry to sound stupid, but where and how do I do this? -- Andrew Nix St Pauls Catholic High School Firbank Road Newall Green Wythenshawe Manchester M23 2YS tel: 0161 4922040 fax: 0161 4982030
--- Andrew Nix
Sorry to sound stupid, but where and how do I do this?
Marks, just re-iterating what I have already said: /etc/init.d/nfs start -- Thomas Adam ===== Thomas Adam "The Linux Weekend Mechanic" -- www.linuxgazette.com ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk
On Fri, Oct 31, 2003 at 09:22:22AM -0000, Andrew Nix wrote:
Mark Evans said:
On Thu, Oct 30, 2003 at 02:45:38PM -0000, Andrew Nix wrote:
The usual approach is to mount all non network filesystems at the start of the boot process. With mounting of network filesystems being done later. i.e. after configuration of the network.
I have had a look through the suse manual but it doest list many examples of options that can be used in fstab. All of them seem quite irrelavent for what I need to do. But also had a search on the net but couldnt Find anything of any help.
IIRC SuSE performs the latter by running a script called "nfs", check this is actually being run.
Sorry to sound stupid, but where and how do I do this?
Have a look to see what startup scripts you have installed. SuSE scripts used to live in /sbin/init.d, but things were rearranged in version 8. So try looking in either /etc/rc.d or /etc/init.d Did you alter /etc/fstab by hand or through Yast? If you altered it by hand try taking the line out and going through Yast, that route should ensure that all the correct scripts are installed and started. (If when you originally set up Yast didn't know about any NFS mounts it probably didn't bother to install the second script.) -- Mark Evans St. Peter's CofE High School Phone: +44 1392 204764 X109 Fax: +44 1392 204763
Did you alter /etc/fstab by hand or through Yast? If you altered it by hand try taking the line out and going through Yast, that route should ensure that all the correct scripts are installed and started.
Originally I just edited /etc/fstab. But I just used the yast method and it mounts properly. Cheers Mark. -- Andrew Nix St Pauls Catholic High School Firbank Road Newall Green Wythenshawe Manchester M23 2YS tel: 0161 4922040 fax: 0161 4982030
--- Andrew Nix
altered it by hand try taking the line out and going through Yast, that route should ensure that all the correct scripts are installed and started.
Originally I just edited /etc/fstab. But I just used the yast method and it mounts properly. Cheers Mark.
Excellent, good to hear it :) Of course, YAST has made all the changes that I told you to do by hand, LOL. -- Thomas Adam ===== Thomas Adam "The Linux Weekend Mechanic" -- www.linuxgazette.com ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://mail.messenger.yahoo.co.uk
participants (3)
-
Andrew Nix
-
Mark Evans
-
Thomas Adam