Bug 64349

 Subject: Re: kern/64313: FreeBSD (OpenBSD) pthread implicit set/unset O_N=
 ONBLOCK flag =
 
 In-Reply-To: Message from Craig Rodrigues <rodrigc@crodrigues.org> =
 
    of "Tue, 16 Mar 2004 13:10:53 EST." <20040316181053.GA2764@crodrigues.=
 org> =
 
 X-Face: eCcoCV}FjV*O{6>[1$XP/e%]TJhEw2MF33dFh)^HM7Gfd=3D[/(4+0a$~<a~$&$fG=
 IkE9,
  Z#ASoDTT`c'^<e2\j?vaa;_VsBAKPw(&{w\d"S&AGJkz{G^*NJtwqVIlh#'Xj+HKe8=3DLS_=
 J"H0
  +nBW8e!F.S"/C[pW||0^.Sin*LOZKcR$@B&w2)I'BD_An!)ZU~$oqer\q*8h(!V9YB;k(@bp=
 ),E
  ~:aN4x.Q/we6{XZ"4t5D^?K}h~
 Mime-Version: 1.0
 Content-Type: text/plain; charset=3Diso-8859-1
 ----------
 
 In reply to Craig Rodrigues who wrote:
 
 >Hi,
 >
 >What is the point of this PR?  It contains
 >a patch to what looks like a program in ports.
 
 Yes, I was only hit by this bug cause I'm the apcupsd maintainer, and =
 
 someone send me the apcupsd workaroung patch.
 
 >The O_NONBLOCK issue with libc_r is known.
 >Take a look at:
 >http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dmisc/41331
 
 Sorry, I've overseen this when looking for pthread issues.
 
 >This problem doesn't occur with the
 >new KSE ( http://www.freebsd.org/kse ) libpthread implementation
 >of threads in FreeBSD 5.x.
 >
 >Most likely this problem will not be fixed in libc_r,
 >since most efforts these days are focused on
 >getting libpthread solid in 5.x.
 >
 >Dan Eischen has been suspending (and not closing) these kinds of PR's, i=
 =2Ee.
 >problems that occur in libc_r but not in libpthread,
 >because most likely they will not be fixed in libc_r
 >(but they may be one day, if someone takes an interest in fixing up libc=
 _r).
 
 Hmm, I understand focussing on 5.X, but there are a lot of production =
 
 machines out there, that will not so soon be updated to 5.X when 4.Y is =
 
 running very stable on them.
 
 So it would be nice if someone could backport the solution.
 
 Best regards
 
 Lars
 
 -- =
 
 Lars K=F6ller
 E-Mail: lars@koellers.net (LKoeller@FreeBSD.ORG)
 -------- FreeBSD, was sonst? ---- http://www.de.freebsd.org --------