On Tue, 19 Apr 2005, Ralf Hildebrandt wrote:
I tried the patch from bugzilla
(http://www.squid-cache.org/bugs/show_bug.cgi?id=1287), but I cannot
apply it.
Which Squid version is this patch against? I'm trying to rebuild 2.5.9
here, but the patch fails:
# patch -p0 < ../patch.squid
patching file sr
I tried the patch from bugzilla
(http://www.squid-cache.org/bugs/show_bug.cgi?id=1287), but I cannot
apply it.
Which Squid version is this patch against? I'm trying to rebuild 2.5.9
here, but the patch fails:
# patch -p0 < ../patch.squid
patching file src/store_client.c
Hunk #1 succeeded at
* Ralf Hildebrandt <[EMAIL PROTECTED]>:
> > Please file a bug report on this issue. Have a patch ready for you.
> Will do
Done, #1287
--
Ralf Hildebrandt (i.A. des IT-Zentrum) [EMAIL PROTECTED]
Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155
Gemeinsame Einri
* Henrik Nordstrom <[EMAIL PROTECTED]>:
> This looks familiar.. fixed another similar problem not long ago.
Well it took me a while... to work around all this #*~=?$ that I had
to go through...
> Please file a bug report on this issue. Have a patch ready for you.
Will do
--
Ralf Hildebrandt (
On Mon, 18 Apr 2005, Ralf Hildebrandt wrote:
Ran squid in gdb again:
(gdb) set args -NsYC
(gdb) handle SIGPIPE pass nostop noprint
SignalStop Print Pass to program Description
SIGPIPE NoNo Yes Broken pipe
Ah, you read the FAQ again?
Program received si
* Ralf Hildebrandt <[EMAIL PROTECTED]>:
> Ran squid in gdb. I got this:
Ran squid in gdb again:
(gdb) set args -NsYC
(gdb) handle SIGPIPE pass nostop noprint
SignalStop Print Pass to program Description
SIGPIPE NoNo Yes Broken pipe
(gdb) run
Starting
* Ralf Hildebrandt <[EMAIL PROTECTED]>:
> This sucks.
Ran squid in gdb. I got this:
# gdb /usr/sbin/squid
...
(gdb) set args -NsYC
(gdb) run
Starting program: /usr/sbin/squid -NsYC
[Thread debugging using libthread_db enabled]
[New Thread -1209899488 (LWP 1968)]
Program received signal SIGPIPE,
On Sat, 16 Apr 2005, Ralf Hildebrandt wrote:
BTW, there's a way: I can use iptables to forward port 888 to 3128!
Indeed. This works fine.
Regards
Henrik
On Fri, 15 Apr 2005, Ralf Hildebrandt wrote:
* Henrik Nordstrom <[EMAIL PROTECTED]>:
What user do you start Squid as? You can't start as root and still have a
core.
And how is Squid supposed to bind to port 888 then?
You can't, unless you manage to convince the kernel to run it with the
proper cap
On Fri, 15 Apr 2005, Ralf Hildebrandt wrote:
* Ralf Hildebrandt <[EMAIL PROTECTED]>:
* Elsen Marc <[EMAIL PROTECTED]>:
http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19
Indeed, the binary had been stripped at installation -- fixed that.
I adjusted the limits and explicitly changed the directo
* Ralf Hildebrandt <[EMAIL PROTECTED]>:
> * Elsen Marc <[EMAIL PROTECTED]>:
>
> > http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19
>
> Indeed, the binary had been stripped at installation -- fixed that.
> I adjusted the limits and explicitly changed the directory before starting
> squid.
* Elsen Marc <[EMAIL PROTECTED]>:
> http://www.squid-cache.org/Doc/FAQ/FAQ-11.html#ss11.19
Indeed, the binary had been stripped at installation -- fixed that.
I adjusted the limits and explicitly changed the directory before starting
squid.
--
_
> I need a hint, squid crashes, but generates no core file.
> It's started this way (from daemontools' supervise):
>
> snip --
> mv /squid-cache0/core /squid-cache0/core-/bin/date +%T
>
> cd /squid-cache0
> touch /squid-cache0/core
> chmod 666 /squid-cache0/core
>
>
13 matches
Mail list logo