...
> ch2ldsladmin:/etc # command-not-found exportfs
> ch2ldsladmin:/etc #
>
> Well, that's real helpful.
Dunno why 'command-not-found' failed to give a clue, since that is its
purpose in life. (But then, I don't use that particular helper ... so
no idea what would make it work (or not).)
I find 'exportfs' in the "nfs-kernel-server" package on one of my systems.
I find it in "nfs-utils" on another system.
What I did was ... (as root so the search is/was correct) ...
which exportfs | xargs rpm -q -f
> Went on to the next item (test the nfs mount):
>
> ch2ldsladmin:/etc # ls /mnt
> ch2ldsladmin:/etc # mount localhost:/var/nfs/sles11sp2/ /mnt
> mount.nfs: rpc.statd is not running but is required for remote locking.
> mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
I would not use "-o nolock". Start 'rpc.statd' on the client side.
Also, just to be painfully clear (because I think I asked before, but
I forget things), you're testing NFS viability by trying to mount this
FS on the same box from which it is served out, yes? NO PROBLEM, but
you'll be doing NFS server and NFS client on the same machine (for the
testing) and we'll need to keep that in mind.
Recommend you not use "localhost" for this testing. Either mount by
addr (icky, but works) or get the box fully into DNS and mount by its
true hostname.
--
-- R; <><
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
