From owner-freebsd-current Sat Oct 17 18:58:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17939 for freebsd-current-outgoing; Sat, 17 Oct 1998 18:58:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17893 for ; Sat, 17 Oct 1998 18:58:00 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id SAA24754; Sat, 17 Oct 1998 18:58:01 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Marc Slemko cc: current@FreeBSD.ORG Subject: Re: sleep() and Apache in release notes In-reply-to: Your message of "Sat, 17 Oct 1998 17:22:24 PDT." Date: Sat, 17 Oct 1998 18:58:01 -0700 Message-ID: <24750.908675881@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (don't know who wrote what part of the release notes, but...) I'm not really sure who wrote that (possibly Garrett, but I wouldn't swear on it) but I'm sorry for the unfortunate choice of words. I should have proof-read the release notes more carefully - mea culpa! I don't think that any intentional slight was meant by it, just an off-the-cuff comment in engineer-speak that problably shouldn't have gone into the public docs. Once we figure out who added it (I'm on a slow link at the moment or I'd inspect the CVS logs), we can determine just what was meant by it. - Jordan > > It is somewhat disappointing to see: > > o sleep(3) and usleep(3) are now implemented in terms of signanosleep(2) > and now have correct SIGALRM interaction semantics and sleep(3) correctly > returns the time remaining. Some programs (notably apache httpd) bogusly > depend on a sleep() "absorbing" a SIGALRM from a timer that expires during > the life of the sleep. > > in RELNOTES.TXT considering I have no idea where the bug in Apache that is > claiming would be and there have been no bug report or attempt to get this > fixed in Apache other than sticking lines in the release notes saying > "Apache is broken". > > If there is a problem in Apache, please point it out so it can be fixed. > > -- > Marc Slemko | Apache Group member > marcs@znep.com | marc@apache.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message