Sort of a noobie at NFS but I seem to have everything
setup prpoerly. However I get the following messages on boot:

Starting NFS services:
/usr/sbin/exportfs -r
exportfs: /etc/exports [5]: No 'sync' or 'async' option specified for export "192.168.0.1:/".
Assuming default behaviour ('sync').
NOTE: this default has changed from previous versions
client.domain.com:/: Function not implemented
/usr/sbin/rpc.rquotad
/usr/sbin/rpc.nfsd 8
/usr/sbin/rpc.mountd
/usr/sbin/rpc.lockd
lockdsvc: Function not implemented
/usr/sbin/rpc.statd

and unfortunately everything seems to be running except nfsd.

rpcinfo -p

program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100011 1 udp 822 rquotad
100011 2 udp 822 rquotad
100011 1 tcp 825 rquotad
100011 2 tcp 825 rquotad
100005 1 udp 825 mountd
100005 1 tcp 828 mountd
100005 2 udp 825 mountd
100005 2 tcp 828 mountd
100005 3 udp 825 mountd
100005 3 tcp 828 mountd
100024 1 udp 832 status
100024 1 tcp 835 status

Shouldn't I be seeing nfs in this output?

export looks like: / 192.168.0.1(rw,no_root_squash)

Is it possible that "client.domain.com:/: Function not implemented"
is the problem? At this point there is a Windows machine at
192.168.0.1 not a Linux box. Even so, shouldn't nfsd be running?

Any help appreciated.

well I have a tutorial here.
Seems you are on the right path though; if you /etc/rc.d/rc.nfsd restart what do you get?
No it shouldn't matter if its a windows machine; you never said anything about access from it (you'd need something like humming bird for that)

My exports file reads:

/home/share dlgbuild(sync,rw,no_root_squash)
/home/share gsbbuild(sync,rw,no_root_squash)

I've got two "build" PC's for packaging stuff and I share out /home/share to copy the finished packages over to my main PC.

rpcinfo -p reads:
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
391002 1 tcp 741 sgi_fam
391002 2 tcp 741 sgi_fam
100011 1 udp 898 rquotad
100011 2 udp 898 rquotad
100011 1 tcp 901 rquotad
100011 2 tcp 901 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100021 1 udp 32771 nlockmgr
100021 3 udp 32771 nlockmgr
100021 4 udp 32771 nlockmgr
100021 1 tcp 53022 nlockmgr
100021 3 tcp 53022 nlockmgr
100021 4 tcp 53022 nlockmgr
100005 1 udp 909 mountd
100005 1 tcp 912 mountd
100005 2 udp 909 mountd
100005 2 tcp 912 mountd
100005 3 udp 909 mountd
100005 3 tcp 912 mountd
100024 1 udp 917 status
100024 1 tcp 920 status

So yes nfs should be showing up if it is working correctly.

Shouldn't matter about "what" is at 192.168.0.1 as long as it is a valid IP address because you are sharing your / and allowing that IP address root access to your /.

Are you *sure* that the IP address is correct? Do you have that PC set to use DHCP? If so then the IP address could change. Also are you using a router? If so, 192.168.0.1 is the "server" IP for most "home" routers that I've worked with so are you positive that is the IP address for the PC.

Later,
MMYoung

Sorry! I thought I had NFS server support compiled
in the kernel. When I looked, as a last step in finding
the problem, it was not checked.

Never fails. Every time I can't seem to track down a config
problem simply, it turns up as a kernel problem.

I think I reached the mistake quota. I am now a full-fledged
member of the idiots club.

Thanks all!

I'm the club president, so welcome to the club!

Later,
MMYoung

Thought you might like to know that none of the 'headings' on that page are hyperlinks ... at least not for me.

Me neither.

MMYoung

Same here.

No they're java script. I find it better than having to write/load an entirely new page
Just click on it (it has no hand-hyperlink icon).

Well, your instructions say "Click on a heading to view."

Thanks.

Ahhh ...