Date: Fri, 15 Nov 2002 22:58:16 +0100 From: Martijn Pronk <martijn@smartie.xs4all.nl> To: Kris Kennaway <kris@obsecurity.org> Cc: "Andrew P. Lentvorski" <bsder@mail.allcaps.org>, current@freebsd.org Subject: Re: rpc.lockd problems Message-ID: <3DD56DF8.6050206@sillywalks.org> References: <20021114171353.A2223-100000@mail.allcaps.org> <3DD497C7.6070700@sillywalks.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Martijn Pronk wrote: >>> "My program" is just anything that attempts to obtain a lock on a file >>> on the NFS filesystem. vi does this when opening an existing file, as >>> does mutt when opening a mailbox. >>> >> >> >> Well, that sure simplifies the problem of running your program. ;) >> >> > Thanks for the info, I will try that tonight after I get back home > from the first > day of the EuroBSDcon. OK, I tested it with a Solaris 8 NFS server with -current as a client, and locking does indeed work. (At least, vi didn't show the word "UNLOCKED" in the bottom line after I enabled rpc.lockd) However, I had some starting problems with rpc.lockd. Aparently it requires that rpc.statd also is running. Since I didn't had these things enabled in rc.conf, I started them manually. rpc.lockd quits silently without logging anything about what happened. The manualpage does mention that rpc.lockd " typically runs in conjunction with rpc.statd" As I don't see a direct requirement in this line, I didn't realize it was required. HTH, Martijn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DD56DF8.6050206>