You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "William A. Rowe, Jr." <wr...@rowe-clan.net> on 2001/05/17 19:26:08 UTC
Apache 1.3.20 rolled and ready for testing
The 1.3.20 tarball is available from http://dev.apache.org/dist/
Seems this announce never went out amidst all the email delivery fooness
on Wednesday.
Schedule is to queue up the announce for first thing tommorow, I'll be
building the win32 binaries late this aftn.
Bill
Re: Apache 1.3.20 rolled and ready for testing
Posted by "William A. Rowe, Jr." <ad...@rowe-clan.net>.
Reports from the ground...
I'll wait till first thing in the morning to hear from any broken folk, but
we look flawless to get this announced on Sunday...
From: "Wilfredo Sanchez" <ws...@MIT.EDU>
To: "William A. Rowe, Jr." <wr...@rowe-clan.net>
Sent: Friday, May 18, 2001 3:19 PM
>
> On Friday, May 18, 2001, at 01:11 PM, William A. Rowe, Jr. wrote:
>
> > Still not sure if you are +1 on release, Fred (I'm not reading it that
> > way.)
>
> Sorry, yes, I'm +1.
From: "Brian Moon" <br...@dealnews.com>
Sent: Friday, May 18, 2001 3:48 PM
>
> +1
>
> running fine on Redhat 7.1/PHP-CVS.
>
Sent: Friday, May 18, 2001 3:59 PM
>
> Also seems to be working fine with Windows and Apache Manager 2.1.
From: <MB...@xomox.de>
Subject: RE: Stable-Testers: Apache 1.3.20 candidate
>
> Apache 1.3.20 compiles and runns fine on:
>
> Host: Sun Ultra 10
> OS: Solaris 7
> CC: gcc 2.95
>
> No compilation- errors, no installation errors, fine performance at low load.
> If there will be something at more or high load, I'll send another mail.
From: "James Sutherland" <ja...@cam.ac.uk>
>
> Apache Server Status for orac.joh.cam.ac.uk
> Server Version: Apache/1.3.20 (Unix)
> Server Built: May 15 2001 20:10:29
>
> Compiled and runs fine on Linux 2.4, serving pages for 2 days without any issues...
From: "David McCreedy" <mc...@us.ibm.com>
>
> In any case, +1 for Apache 1.3.20 on IBM's TPF platform.
----- Original Message -----
From: "William A. Rowe, Jr." <wr...@rowe-clan.net>
To: <ne...@apache.org>
Sent: Thursday, May 17, 2001 12:26 PM
Subject: Apache 1.3.20 rolled and ready for testing
> The 1.3.20 tarball is available from http://dev.apache.org/dist/
>
> Seems this announce never went out amidst all the email delivery fooness
> on Wednesday.
>
> Schedule is to queue up the announce for first thing tommorow, I'll be
> building the win32 binaries late this aftn.
>
> Bill
>
>
>
Re: Apache 1.3.20 rolled and ready for testing
Posted by "William A. Rowe, Jr." <ad...@rowe-clan.net>.
You are right, sending now... thanks!
----- Original Message -----
From: "Roy T. Fielding" <fi...@ebuilt.com>
To: <ne...@apache.org>
Sent: Thursday, May 17, 2001 2:12 PM
Subject: Re: Apache 1.3.20 rolled and ready for testing
> On Thu, May 17, 2001 at 12:26:08PM -0500, William A. Rowe, Jr. wrote:
> > The 1.3.20 tarball is available from http://dev.apache.org/dist/
> >
> > Seems this announce never went out amidst all the email delivery fooness
> > on Wednesday.
> >
> > Schedule is to queue up the announce for first thing tommorow, I'll be
> > building the win32 binaries late this aftn.
>
> No announcement goes out until we have three +1 for a release from people
> who have tested the tarball, after which we move the tarball to
> www.apache.org/dist/httpd, and 24 hours after that we make the announcement
> to the announcement list. Right now a message should be sent to
> stable-testers so that they can pick it up.
>
> ....Roy
>
>
Re: Apache 1.3.20 rolled and ready for testing
Posted by James Sutherland <ja...@cam.ac.uk>.
On Thu, 17 May 2001, Roy T. Fielding wrote:
> On Thu, May 17, 2001 at 12:26:08PM -0500, William A. Rowe, Jr. wrote:
> > The 1.3.20 tarball is available from http://dev.apache.org/dist/
> >
> > Seems this announce never went out amidst all the email delivery fooness
> > on Wednesday.
> >
> > Schedule is to queue up the announce for first thing tommorow, I'll be
> > building the win32 binaries late this aftn.
>
> No announcement goes out until we have three +1 for a release from people
> who have tested the tarball, after which we move the tarball to
> www.apache.org/dist/httpd, and 24 hours after that we make the announcement
> to the announcement list. Right now a message should be sent to
> stable-testers so that they can pick it up.
Apache Server Status for orac.joh.cam.ac.uk
Server Version: Apache/1.3.20 (Unix)
Server Built: May 15 2001 20:10:29
Current Time: Friday, 18-May-2001 00:06:53 BST
Restart Time: Tuesday, 15-May-2001 21:09:24 BST
Parent Server Generation: 0
Server uptime: 2 days 2 hours 57 minutes 29 seconds
Total accesses: 25980 - Total Traffic: 262.9 MB
CPU Usage: u21.21 s23.71 cu0 cs0 - .0245% CPU load
.142 requests/sec - 1502 B/second - 10.4 kB/request
1 requests currently being processed, 9 idle servers
Compiled and runs fine on Linux 2.4, serving pages for 2 days without any
issues...
James.
--
"Our attitude with TCP/IP is, `Hey, we'll do it, but don't make a big
system, because we can't fix it if it breaks -- nobody can.'"
"TCP/IP is OK if you've got a little informal club, and it doesn't make
any difference if it takes a while to fix it."
-- Ken Olson, in Digital News, 1988
Re: Apache 1.3.20 rolled and ready for testing
Posted by "Roy T. Fielding" <fi...@ebuilt.com>.
On Thu, May 17, 2001 at 12:26:08PM -0500, William A. Rowe, Jr. wrote:
> The 1.3.20 tarball is available from http://dev.apache.org/dist/
>
> Seems this announce never went out amidst all the email delivery fooness
> on Wednesday.
>
> Schedule is to queue up the announce for first thing tommorow, I'll be
> building the win32 binaries late this aftn.
No announcement goes out until we have three +1 for a release from people
who have tested the tarball, after which we move the tarball to
www.apache.org/dist/httpd, and 24 hours after that we make the announcement
to the announcement list. Right now a message should be sent to
stable-testers so that they can pick it up.
....Roy
Re: Apache 1.3.20 rolled and ready for testing
Posted by "William A. Rowe, Jr." <ad...@rowe-clan.net>.
From: "Wilfredo Sanchez" <ws...@MIT.EDU>
Sent: Thursday, May 17, 2001 7:48 PM
> On Thursday, May 17, 2001, at 05:39 PM, Wilfredo Sanchez wrote:
>
> > And it exits with an entry in the error log:
> >
> > [Thu May 17 17:36:23 2001] [alert] mod_unique_id: unable to
> > gethostbyname("bartleby")
>
> The offending code is below. It seems rather inappropriate to me for
> a module to be calling exit() under any circumstances. For one thing,
> the pid file doesn't get cleaned up. But apparently a lot of modules do
> this... Something to clean up in 2.0...
Feel free to patch the offensive [uhm... offending] code for 1.3.21 as well,
if you have the itch.
> Anyway, the reason it didn't happen before is that I didn't enable
> that module before, so that's my bad; the code's been there a long time.
That would do it :-)
Thanks for the update.
> Never mind me.
We don't.
Bill
Re: Apache 1.3.20 rolled and ready for testing
Posted by Sander Temme <sc...@covalent.net>.
on 5/17/01 5:48 PM, Wilfredo Sanchez at wsanchez@MIT.EDU wrote:
> Anyway, the reason it didn't happen before is that I didn't enable
> that module before, so that's my bad; the code's been there a long time.
IIRC it's in the --enable-shared=most collection in Apache 1.3. I *have* run
into it before because I tend to install Apache on boxes that are not
correctly named in the local DNS.
S.
--
Covalent Technologies sctemme@covalent.net
Engineering group Voice: (415) 536 5214
645 Howard St. Fax: (415) 536 5210
San Francisco CA 94105
PGP Fingerprint: 1E74 4E58 DFAC 2CF5 6A03 5531 AFB1 96AF B584 0AB1
=======================================================
This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and destroy all copies
of the original message
=======================================================
Re: Apache 1.3.20 rolled and ready for testing
Posted by Wilfredo Sanchez <ws...@MIT.EDU>.
On Thursday, May 17, 2001, at 05:39 PM, Wilfredo Sanchez wrote:
> And it exits with an entry in the error log:
>
> [Thu May 17 17:36:23 2001] [alert] mod_unique_id: unable to
> gethostbyname("bartleby")
The offending code is below. It seems rather inappropriate to me for
a module to be calling exit() under any circumstances. For one thing,
the pid file doesn't get cleaned up. But apparently a lot of modules do
this... Something to clean up in 2.0...
Anyway, the reason it didn't happen before is that I didn't enable
that module before, so that's my bad; the code's been there a long time.
Never mind me.
-Fred
/*
* Now get the global in_addr. Note that it is not sufficient to
use one
* of the addresses from the main_server, since those aren't as
likely to
* be unique as the physical address of the machine
*/
if (gethostname(str, sizeof(str) - 1) != 0) {
ap_log_error(APLOG_MARK, APLOG_NOERRNO|APLOG_ALERT, s,
"gethostname: mod_unique_id requires the "
"hostname of the server");
exit(1);
}
str[sizeof(str) - 1] = '\0';
if ((hent = gethostbyname(str)) == NULL) {
ap_log_error(APLOG_MARK, APLOG_NOERRNO|APLOG_ALERT, s,
"mod_unique_id: unable to gethostbyname(\"%s\")",
str);
exit(1);
}
Re: Apache 1.3.20 rolled and ready for testing
Posted by Wilfredo Sanchez <ws...@MIT.EDU>.
Since when do I have to have a host entry for my machine in order to
run httpd? I computer thinks its hostname is 'bartleby'. There is no
DNS entry for it, nor an /etc/hosts entry, since it gets its IP via
DHCP. When I try to launch Apache, it complains:
[Thu May 17 17:36:23 2001] [alert] httpd: Could not determine the
server's fully qualified domain name, using 127.0.0.1 for ServerName
And it exits with an entry in the error log:
[Thu May 17 17:36:23 2001] [alert] mod_unique_id: unable to
gethostbyname("bartleby")
This is new; previously it launched OK. If I set ServerName in
httpd.conf, the complaint to stderr goes away, but the log entry is
still there and the server still exits.
I reckon I can add bartleby to /etc/hosts as an alias for localhost, but
it looks like one part of the server thinks it can deal, and another is
bailing out. Anyway, this used to work.
-Fred