🚀 go-pugleaf

Paul Woods writes
> In article <12105@tamsun.tamu.edu> cnh5730@maraba.tamu.edu (Charles Herrick)  
> writes:
> > I've changed export information in /etc/exports and then did the following  
> > on many NeXTs:
> > 	% exportfs -uav
> > 	% exportfs -av
> > 
> > only to have to reboot the NeXT NFS server because the damn
> > 	EXPORTFS
> > didn't work!!
> > 
> > Now, I don't even think twice. My rule is:
> > 	If you changed /etc/exports ...
> > 1) do exportfs -uav
> > 2) then reboot.
> > 3) no kidding.
> > 
> > 	chuck
> > 
> > 
> 
> I don't know why you have to re-boot, but you should not have to.  I make  
> changes to the /etc/exports file on many NeXT's on a daily basis (don't ask)  
and  
> never have to re-boot.  One thing that you might want to try is picking up a  
> product called NFS/TEST from Intercon Corp. (you need a mac to run it) and  
you  
> will be able to see if your d's are up and running properly.
> 
>  

Ok, guys, look in the /etc/rc file.  The NFS stuff isn't run unless  
/etc/exports exists.

Thus the FIRST time you create /etc/exports, the daemons aren't running, and  
you either have to start them by hand, or reboot.

Changing an EXISTING exports command only requires that you run exportfs with  
the appropriate flags afterword.

Hope this clears things up a bit.

sherwood