Need nfs on new install

[Joseph Loo]

On 07/08/2012 08:31 PM, Gene Heskett wrote:
> On Sunday 08 July 2012 23:06:55 Joseph Loo did opine:
>
>> On 07/08/2012 07:20 PM, Gene Heskett wrote:
>>> Greetings;
>>>
>>> I did have nfs working to two other machines, just the /home/myname
>>> directories from this machine to a pair of 10.04-4-LTS installs in my
>>> shop. That was with an uptodate pclos install on this box, but I got
>>> tired of the stuff pclos wouldn't let me do, so I installed that same
>>> 10.04-4 LTS on this machine.  I have installed enough kde that I can
>>> run kmail & play some games, but nowhere near all of it.
>>>
>>> autofs is installed and running, and I have exported the /home/me
>>> share in /etc/exports.  And which cannot be seen by either of the
>>> shop machines.
>>>
>>> No nfs shares are showing on either end of the cat5, regardless of how
>>> many times I restart autofs.
>>>
>>> Then looking for help, I typed man nfs and get instructions on how to
>>> add a stanza or two to my /etc/fstab, something I never had to do
>>> before! I have 3 former main drives here, nfs worked with a pclos
>>> install, it worked with a mandriva install, and neither of those
>>> fstabs have a thing about nfs mounts in them.  The 3rd drive did have
>>> centos6.2 on it, but I couldn't get so much stuff to work there it
>>> only lasted 2 weeks.
>>>
>>> So what do I do next?
>>>
>>> Thanks for any help.
>>>
>>> Cheers, Gene
>> On the machine that is exporting the directories do:
>>       sudo exportfs
> No response, just a prompt back on this machine. Both of the others return:
> /home/gene    	<world>
>> On the client machine:
>>      ifconfig
>  From shop.coyote.den:
> gene at shop:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 38:60:77:4e:38:1b
>            inet addr:192.168.71.4  Bcast:192.168.71.255  Mask:255.255.255.0
>            inet6 addr: fe80::3a60:77ff:fe4e:381b/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:80500 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:24594 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:70784959 (70.7 MB)  TX bytes:1945144 (1.9 MB)
>            Interrupt:28 Base address:0x8000
>
>  From lathe.coyote.den:
> gene at lathe:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 38:60:77:cd:f3:2f
>            inet addr:192.168.71.5  Bcast:192.168.71.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:260969 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:310847 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:92777292 (92.7 MB)  TX bytes:140936682 (140.9 MB)
>            Interrupt:28
>
> And from coyote.coyote.den (this machine):
> gene at coyote:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:1f:c6:62:fc:bb
>            inet addr:192.168.71.3  Bcast:192.168.71.255  Mask:255.255.255.0
>            inet6 addr: fe80::21f:c6ff:fe62:fcbb/64 Scope:Link
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:2881452 errors:0 dropped:0 overruns:0 frame:0
>            TX packets:2146510 errors:0 dropped:0 overruns:0 carrier:0
>            collisions:0 txqueuelen:1000
>            RX bytes:2778075683 (2.7 GB)  TX bytes:470319302 (470.3 MB)
>            Interrupt:26 Base address:0x2000
>
>> List the contents of auto.master and the auto.xxx that is going to
>> import the files.
> coyote/etc/auto-master (I don't think its been touched)
> #
> # Sample auto.master file
> # This is an automounter map and it has the following format
> # key [ -mount-options-separated-by-comma ] location
> # For details of the format look at autofs(5).
> #
> #/misc	/etc/auto.misc
> #
> # NOTE: mounts done from a hosts map will be mounted with the
> #	"nosuid" and "nodev" options unless the "suid" and "dev"
> #	options are explicitly given.
> #
> #/net	-hosts
> #
> # Include central master map if it can be found using
> # nsswitch sources.
> #
> # Note that if there are entries for /net or /misc (as
> # above) in the included master map any keys that are the
> # same will not be seen as the first read key seen takes
> # precedence.
> #
> +auto.master
>
>> If you enable auto.net what does ls /net/nfs server name
>> show?
>>
>> When you altered the auto.xxx file did you restart autofs?
> I have not that I can recall, ever modified an auto.* file to make it work
> on other installs, so what am I expected to do with them, preferably so it
> works both ways for all 3 machines.  I also don't seem to have an
> /etc/auto.xxx file on any of the 3 machines.
>
> Thank you Joseph Loo
>
> Cheers, Gene
Looks like you have nis+ configured for your system. What is your 
configuration for the auto.master for nis+ and its directories?

If you remove "#" on /net and the nfsserver is on your host file then 
you can try
ls /net/nfsserver name and see what is coming up.

-- 
Joseph Loo
jloo at acm.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20120709/5157b454/attachment.html>