Thanks to
Iwao Makino
Bochnik, William J
Frank Wortner
Knut Hellebų
Ian Mortimer
J. Dean Brock
Lindsay Wakeman
for replying.
My problem was to do with mounting Tru64 file systems via NFS from
SuSE 7.0 clients. I have two Tru64 servers A and B and:
SuSE 6.4 clients can mount from either machine
SuSE 7.0 clients can mount from A, not B
rpcinfo -p A just hangs
I'll give some of the replies in full, but very briefly my conclusions
are:
(1) this problem has been seen with RedHat clients too
(2) nobody knows what causes it
(3) I can't restart tru64 portmap without unmounting NFS file systems
(4) There is a superior version of portmap available from
ftp://ftp.porcupine.org/pub/security/portmap_4.tar.gz which can be
restarted
(5) Tru64 can't expect to compete with Linux when essential programs
such as
portmap
TCP wrappers
bash
up-to-date Perl
ssh
(just for starters) have to be downloaded, compiled and installed.
Here are some of the replies:
Frank Wortner:
Portmap's information is unfortunately volatile. It keeps the
registered RPC ports list in memory. If you kill the running portmap
process, you will need to reload the new portmap process with the
current registered information. Wietse Venema (the author of the popular
TCP Wrappers programs) includes programs which do exactly that in his TCP
Wrapper enabled portmap
distribution:
ftp://ftp.porcupine.org/pub/security/portmap_4.tar.gz
Just use the pmap_dump and pmap_set programs from that distribution to
extract the current portmap registrations and reload them into a new
instance of portmap.
Knut Hellebo:
If mounting from other systems work there shouldn't be any problems with
the portmapper. Did you do a 'rpcinfo -b 100005 1' from a client to see
if the Tru64 box answers mount requests (perhaps you should also try
probing version 3 and the nfs rpc).
Ian Mortimer:
Had a similar problem here with RedHat 6.2. Boxes running
RedHat 6.1 had no problems mounting from anywhere but boxes
running 6.2 wouldn't mount from just one server (although they
could mount fine from other servers running the same version
of Tru64).
Stopping and restarting the daemons didn't work but a reboot of the
problem server fixed it. (I also didn't want to reboot the server
but a faulty UPS solved it for me by shutting all the servers down
for no good reason).
Received on Fri Oct 13 2000 - 14:47:21 NZDT