On Sun, Nov 17, 2002 at 09:31:40PM +0100, Martijn Pronk wrote:
> I hope this is enough info for you, if you need a real dump to look
> at yourself, just let me know, I'll put it online then.
Thanks, but the binary dump would be more useful so I can read it into
ethereal. ethereal does a really g
Andrew P. Lentvorski wrote:
Can you produce a packet trace for Kris? This would give him a known good
trace so that he can point out the differences from his particular
configuration, or, alternatively, he could file a bug report with the
Linux folks.
Ok, here is a but of output from tcpudmp,
On Fri, 15 Nov 2002, Martijn Pronk wrote:
> However, I had some starting problems with rpc.lockd.
> Aparently it requires that rpc.statd also is running.
Hmmm, it shouldn't fail if rpc.statd isn't enabled, but it should probably
complain loudly. Make sure you file a FreeBSD bug report on that, a
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 wi
On Thu, Nov 14, 2002 at 01:47:43AM -0800, Andrew P. Lentvorski wrote:
> On Wed, 13 Nov 2002, Kris Kennaway wrote:
>
> > Yes, and I have no problems interoperating NFS under 4.x between these
> > machines (or under 5.0 as long as I don't try and lock any files) -
> > it's just 5.0's rpc.lockd.
>
>
On Wed, 13 Nov 2002, Kris Kennaway wrote:
> Yes, and I have no problems interoperating NFS under 4.x between these
> machines (or under 5.0 as long as I don't try and lock any files) -
> it's just 5.0's rpc.lockd.
Can you help isolate the problem by trying this same operation from a
Solaris NFS c
On Wed, Nov 13, 2002 at 06:13:21PM -0800, Terry Lambert wrote:
> Kris Kennaway wrote:
> > A few months ago I posted about rpc.lockd interop problems I am having
> > between my 5.0 NFS client and a Redhat 7.1 server. Both are running
> > rpc.lockd, but when I send a lock request to the server it ha
Kris Kennaway wrote:
> A few months ago I posted about rpc.lockd interop problems I am having
> between my 5.0 NFS client and a Redhat 7.1 server. Both are running
> rpc.lockd, but when I send a lock request to the server it hangs
> forever blocked on the /var/run/lock socket.
>
> tcpdump shows t
* Kris Kennaway <[EMAIL PROTECTED]> [021113 16:41] wrote:
> A few months ago I posted about rpc.lockd interop problems I am having
> between my 5.0 NFS client and a Redhat 7.1 server. Both are running
> rpc.lockd, but when I send a lock request to the server it hangs
> forever blocked on the /var/
A few months ago I posted about rpc.lockd interop problems I am having
between my 5.0 NFS client and a Redhat 7.1 server. Both are running
rpc.lockd, but when I send a lock request to the server it hangs
forever blocked on the /var/run/lock socket.
tcpdump shows that the lock RPC request is being
10 matches
Mail list logo
