FreeBSD 5.0: checking "TCP_NODELAY setting is inherited" hangs system
Hi, I got the latest apr from CVS, and when I tried to configure it, it locks up my machine hard. The last step it runs before hanging is: checking if TCP_NODELAY setting is inherited from listening sockets Has anyone seen this before? I could reproduce this on my machine running this kernel: FreeBSD 5.0-CURRENT #18: Mon Feb 24 06:06:47 EST 2003 I had to power cycle the machine after this step because the machine was totally hung. -- Craig Rodrigues http://home.attbi.com/~rodrigc [EMAIL PROTECTED]
Re: FreeBSD 5.0: checking "TCP_NODELAY setting is inherited" hangs system
Craig Rodrigues wrote: Hi, I got the latest apr from CVS, and when I tried to configure it, it locks up my machine hard. The last step it runs before hanging is: checking if TCP_NODELAY setting is inherited from listening sockets Has anyone seen this before? (I assume you know what "locks up my machine hard" means and it isn't simply that configure stalled. Not that configure should stall, but still...) I haven't seen this on FreeBSD 5.0, but I haven't run CURRENT. I would recommend upgrading to the latest CURRENT and, if the problem still exists, report this to the FreeBSD folks ASAP. Depending on how it is resolved and how long it was broken, perhaps we can add a test to fail the configure on the broken FreeBSD levels and point out that an update is necessary.
Re: FreeBSD 5.0: checking "TCP_NODELAY setting is inherited" hangs system
On Fri, Mar 21, 2003 at 01:28:07PM -0500, Jeff Trawick wrote: > Craig Rodrigues wrote: > >Hi, > > > >I got the latest apr from CVS, and when I tried to configure it, > >it locks up my machine hard. The last step it runs before hanging is: > > > >checking if TCP_NODELAY setting is inherited from listening sockets > > >Has anyone seen this before? > > (I assume you know what "locks up my machine hard" means and it isn't > simply that configure stalled. Not that configure should stall, but > still...) When I say "locks up my machine hard", I really mean it. The machine becomes unresponsive at the keyboard, and network connectivity stops (the machine does not respond to pings, and new ssh/telnet connections cannot be made). I did not set up a debug kernel on my second machine, so I did not break into ddb to see if I could figure out where it had hung. -- Craig Rodrigues http://home.attbi.com/~rodrigc [EMAIL PROTECTED]
Re: FreeBSD 5.0: checking "TCP_NODELAY setting is inherited" hangs system
> > checking if TCP_NODELAY setting is inherited from listening sockets > > > Has anyone seen this before? > > (I assume you know what "locks up my machine hard" means and it isn't > simply that configure stalled. Not that configure should stall, but > still...) > > I haven't seen this on FreeBSD 5.0, but I haven't run CURRENT. I usually update my FreeBSD-current box every two or three days and apache 2.1.0-dev on it every week or so but I have never seen this. hiro hanai
Re: FreeBSD 5.0: checking "TCP_NODELAY setting is inherited" hangs system
On Sat, Mar 22, 2003 at 08:31:39PM +0900, hiroyuki hanai wrote: > > > checking if TCP_NODELAY setting is inherited from listening sockets > > > > > Has anyone seen this before? > > > > (I assume you know what "locks up my machine hard" means and it isn't > > simply that configure stalled. Not that configure should stall, but > > still...) > > > > I haven't seen this on FreeBSD 5.0, but I haven't run CURRENT. > > I usually update my FreeBSD-current box every two or three days > and apache 2.1.0-dev on it every week or so but I have never > seen this. OK, my problem went away when I updated -CURRENT to FreeBSD rincewind 5.0-CURRENT FreeBSD 5.0-CURRENT #17: Sat Mar 22 12:29:32 EST 2003 Thanks. -- Craig Rodrigues http://home.attbi.com/~rodrigc [EMAIL PROTECTED]
