Re: lockd errors
CaT (cat@zip.com.au)
Sun, 15 Aug 1999 12:34:03 +1000
On Sun, Aug 15, 1999 at 12:41:03AM +0100, Alan Cox wrote:
> > And what if the server is Solaris? Same problem (at least in 2.2.10);
> > get "failed to monitor" messages and no programs that use flock() or
> > fcntl() will get their lock. This is a real pain using MUA on NFS
> > mounted spool, and using dotlocking is rather silly don't you think?.
>
> Make sure you are running lock daemons on the Solaris box. This case definitely
> works. I've used it
Yup. I get no errors with the solaris box. I just got them with the 2.0.x
box which nolock made go away. Maybe someday soon we'll even upgrade it. 8)
--
CaT (cat@zip.com.au) URL: http://www.zip.com.au/dev/null
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/