[TriLUG] NFS,Autofs,NIS and FC2

Matthew Lavigne maillist at shenandoahkennels.net
Wed Jun 9 05:53:39 EDT 2004


On Tuesday 08 June 2004 19:09, Kevin Flanagan wrote:
> Hey all,
> 	I currently have the following issue that may be related to changes
> with FC2.  The config outlined below works just fine with FC1, but
> doesn't completely work with FC2, I can't figure it out.
>
>
> A Clarkconnect system as my master NFS and NIS server
> uname -a yields "2.4.20-28.9 #1 Thu Dec 18 13:45:22 EST 2003 i686 i686
> i386 GNU/Linux" - This is 192.168.0.206
>
> I have an exports as such,
>
> /kits           192.168.0.0/255.255.255.0(insecure,rw,sync,no_root_squash)
> /home           192.168.0.0/255.255.255.0(rw,sync,no_root_squash)

Try adding insecure as in (insecure,rw,sync,no_root_squash) and see what 
happens.  I was getting a similar issue where NFS installs would not mount 
and I used the system-config-nfs tool on the server side to set it up and is 
was fine.



<snip>
> I can log into the FC2 system as root just fine, when I try to log on as
> myself I get told that my homedir isn't available.  When I log on as
> root I have the stuff under /misc available just fine, kits under it
> etc.
log on to a console and tail -f /var/log/messages and see what the automounter 
spits out as an error.  Just to verify you have flushed iptables to see if 
the firewall is causing you issues right (yes I know you can mount one and 
not the other but ya never know.)


Matthew 



More information about the TriLUG mailing list