Linux NFS development
 help / color / mirror / Atom feed
From: Ruben van Royen <ruben@guidedbees.com>
To: nfs@lists.sourceforge.net
Subject: Locking on HP-UX
Date: Tue, 7 May 2002 19:56:47 +0200	[thread overview]
Message-ID: <20020507195647.B27332@tor.guidedbees.com> (raw)

Hi all, 

I'm having trouble getting file locking to work on hpux. I already searched
your archives, but cannot find the problem from there. 
I have statd and lockd running, and also set insecure_locks. All to no avail.
The request does arrive at the linux client, I can see the ip-nr. of the hpux
machine in /var/lib/nfs/statd/sm after trying to lock a file. But apperently 
the hp does not like the answer it receives. 

I'm running a redhat 7.2 server with 2.4.9-31 redhat kernel and hpux 11.00
on the client.

File locking does work from both sun and linux clients.

Ruben

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

                 reply	other threads:[~2002-05-07 17:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020507195647.B27332@tor.guidedbees.com \
    --to=ruben@guidedbees.com \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox