On Tue, 5 Dec 2000, Henry House wrote:
> Can anyone help with my odd NFS problem? I have three machines, one of which
> is a mail server. The other two machines mount /var/spool/mail over NFS with
> read/write permissions. This worked great until a few days ago, when both
> clients started complaining about RPC problems like so:
[...]
> Dec 5 02:37:17 mycroft kernel: nsm_mon_unmon: rpc failed, status=-13
> Dec 5 02:37:17 mycroft kernel: lockd: failed to monitor 207.215.68.163
>
> What's more, mutt complains that the mailboxes are read-only and other mail
> clients fail to work at all. But this files are not read-only -- I can edit
> them with vim without difficulty. Evidently mutt and other apps are unable to
> lock the mailboxes, but the server does have lockd running and I have tried
> re-starting it with no effect. I'm stumped :-(.
google sez... "are you running rpc.statd on the client?"
I don't know much about rpc, except that port 111 is often used to
gather info for cracking.
---------------------------------------------------------------------------
Jeff Newmiller The ..... ..... Go Live...
DCN:<[EMAIL PROTECTED]> Basics: ##.#. ##.#. Live Go...
Work:<[EMAIL PROTECTED]> Live: OO#.. Dead: OO#.. Playing
Research Engineer (Solar/Batteries O.O#. #.O#. with
/Software/Embedded Controllers) .OO#. .OO#. rocks...2k
---------------------------------------------------------------------------
