From: Randolph Chung <tausq@debian.org>
To: parisc-linux@thepuffingroup.com
Cc: debian-hppa@lists.debian.org
Subject: Re: file locking problems?
Date: Sun, 8 Oct 2000 22:53:24 -0700 [thread overview]
Message-ID: <20001008225324.C639@tausq.org> (raw)
In-Reply-To: <20001008200047.B639@tausq.org>; from randolph@tausq.org on Sun, Oct 08, 2000 at 08:00:48PM -0700
> update-passwd (a Debian package) makes a call to lckpwdf. That fails
> with an "Invalid argument" message. It looks like lckpwdf internally uses
> fcntl() locking, so I tried that and it too fails with an "Invalid
> argument" message. This happens both on nfs and local ext2 fs.
> Similar tests with flock() seems to work ok.
as it turns out, it looks like there's a glibc<->kernel mismatch.
the kernel defines F_RDLCK as 1, and glibc has it defined as 0. dhd is
aware of this and say he'll look into fixing this later this week.
randolph
--
Debian Developer <tausq@debian.org>
http://www.TauSq.org/
prev parent reply other threads:[~2000-10-09 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-09 3:00 [parisc-linux] file locking problems? Randolph Chung
2000-10-09 3:52 ` David Huggins-Daines
2000-10-09 5:53 ` Randolph Chung [this message]
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=20001008225324.C639@tausq.org \
--to=tausq@debian.org \
--cc=debian-hppa@lists.debian.org \
--cc=parisc-linux@thepuffingroup.com \
/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