This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Fwd: [PATCH] glibc-2.2.5 utmp_file locking and locking question]

From: Ulrich Drepper <drepper at redhat dot com>
To: Roland McGrath <roland at frob dot com>
Cc: "Amit D. Chaudhary" <amitc at brocade dot com>, libc-alpha at sources dot redhat dot com
Date: Sun, 25 Aug 2002 16:00:32 -0700
Subject: Re: [Fwd: [PATCH] glibc-2.2.5 utmp_file locking and locking question]
References: <20020825201458.DCD001BA1B@perdition.linnaean.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Roland McGrath wrote:

The only possible error should be EINTR.  But it does seem reasonable to
check for it.  Hmm, actually ENOLCK and EDEADLK might be possible too.

Does anyone know a reason to ignore the fcntl result?

No reason but that it seemed unnecessary.

- -- - ---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE9aWGU2ijCOnn/RHQRApBVAJ9ZVb1/Jd0XoCpbptTU6KSJeFcR1wCcCshA
VTrMutS4A8A3xpAk0G8mQfE=
=6uyC
-----END PGP SIGNATURE-----

Follow-Ups:
- Re: [Fwd: [PATCH] glibc-2.2.5 utmp_file locking and locking question]
  - From: Roland McGrath

References:
- Re: [Fwd: [PATCH] glibc-2.2.5 utmp_file locking and locking question]
  - From: Roland McGrath

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]