by Every once in a while, I get these messages from syslog:
/----
| Apr 17 19:28:37 lucy /sbin/rpc.statd[474]: Attempt to register callback to service 16
| Apr 17 19:28:37 lucy /sbin/rpc.statd[474]: STAT_FAIL to 127.0.0.1 for SM_MON of 129.217.20.159
| Apr 17 19:28:37 lucy kernel: lockd: cannot monitor 129.217.20.159
\----
What do they mean?
I guess the last one means that lockd cannot talk to 129.217.20.159.
I'm not surprised as that is a Solaris machine (lucy is Debian/potato
ix86, running a 2.2.19 kernel), and I've figured out that file locking
via NFS is a problem.
I'm running the userland nfs daemon.
But what do the other messages mean?
Btw, is there any chance for me to get file locking via NFS working
between Linux and Solaris? I'd really like to have that. I would go
to a 2.4 kernel, and I would go to kernel nfs, but only if there is
hope that this helps. My recent forays into kernel-land nfs were not
so promising at all -- other Linux machines still running user-land
nfs were unable to mount my file systems.
Why is file locking important to me? Well, /var/mail lives on a
partition mounted via NFS from a Solaris machine (don't ask).
Therefore, I'd really like to have file locking with Solaris as server
and Linux as client. And the only machine with outside connectivity
is a Solaris machine which mounts my home dir from a Linux machine,
and ncftp wants to lock a file in my home dir. That's the (much less
important) reason I'd like file locking with Linux as server and
Solaris as client.
tia,
kai
--
Be indiscrete. Do it continuously.