From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "Beau E. Cox" <beau@beaucox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.23-pre7,pre8,pre9 hang on starting squid
Date: Thu, 6 Nov 2003 12:06:14 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.44.0311061204510.8534-100000@logos.cnet> (raw)
In-Reply-To: <200311030708.09283.beau@beaucox.com>
On Mon, 3 Nov 2003, Beau E. Cox wrote:
> [1.] summary:
>
> 2.4.23-pre7,pre8,pre9 hang depending on when 'squid' is started.
>
> [2.] Full description:
>
> Running up-to-date Sorcerer.
>
> One machine hangs consistently when this sequence of daemons
> is started in runlevel 3:
>
> S26networking ifconfig etho, eth1, eth1:1 & routes
> S28firewall firewall viaiptables
> S30portmap 5beta
> S32ntpd 4.2.0
> S34named bind 9.2.3
> S36nfs
> S38rpc.bootparamd
> S40xinetd
> S42squid 2.5.STABLE4
> S44mysql 4.0.15a
> S46xmail xmailserver mail server 1.17
> S48spamd
> S50apachectl 2.0.48
>
> It works flawlessly when squid is put to the bottom:
>
> S26networking
> S28firewall
> S30portmap
> S32ntpd
> S34named
> S36nfs
> S38rpc.bootparamd
> S40xinetd
> S42mysql
> S44xmail
> S46spamd
> S48apachectl
> S50squid
>
> Why am I bothering you kernel folks with what looks like a pure
> SA problem?
>
> 1. This machine works flawlessly (with squid started before
> mysql, etc.) unter 2.4.22.
> 2. Four other machines running the same software (I compile
> my own packages via Sorcerer) using 2.4.23-pre9 and squid
> above.
> 3. This problem is solid on this one machine. Always reproduceable.
> Always hangs with squid. No dumps found. Just HANG.
Strange.
Can you find out in which -pre the problem starts?
next prev parent reply other threads:[~2003-11-06 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 17:08 PROBLEM: 2.4.23-pre7,pre8,pre9 hang on starting squid Beau E. Cox
2003-11-06 14:06 ` Marcelo Tosatti [this message]
2003-11-06 17:49 ` Beau E. Cox
2003-11-07 16:00 ` Beau E. Cox
2003-11-07 23:51 ` Randy.Dunlap
2003-11-08 10:31 ` Beau E. Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0311061204510.8534-100000@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=beau@beaucox.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).