This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [Fwd: [PATCH] glibc-2.2.5 utmp_file locking and lockingquestion]
- From: "Amit D. Chaudhary" <amitc at brocade dot com>
- To: "Roland McGrath" <roland at frob dot com>
- Cc: <libc-alpha at sources dot redhat dot com>, "Ulrich Drepper" <drepper at redhat dot com>
- Date: Sun, 25 Aug 2002 19:39:22 -0700
- Subject: Re: [Fwd: [PATCH] glibc-2.2.5 utmp_file locking and lockingquestion]
- References: <20020825231407.832521BA1B@perdition.linnaean.org>
Thanks, will pull these in.
Regards
Amit
----- Original Message -----
From: Roland McGrath <roland@frob.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Amit D. Chaudhary <amitc@brocade.com>; <libc-alpha@sources.redhat.com>
Sent: Sunday, August 25, 2002 4:14 PM
Subject: Re: [Fwd: [PATCH] glibc-2.2.5 utmp_file locking and
lockingquestion]
> > -----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.
>
> They may be obscure and vanishingly rare, but there are cases that could
fail.
> I have put the checks in.
>