tis 2008-04-01 klockan 00:18 +1300 skrev Amos Jeffries:
The merge It would be a whole lot cleaner and actually less change
overall if we could drop the TPROXY version 2 support from Squid-3.
+1
Regards
Henrik
mån 2008-03-31 klockan 08:26 -0600 skrev Alex Rousskov:
We may be able to provide better comments when we see the current code.
It does not have to be polished and ready for commit.
I see no reason to continue supporting now obsolete and no longer
supported TPROXY versions in new versions of
On Mon, 2008-03-31 at 20:28 +0200, Henrik Nordstrom wrote:
mån 2008-03-31 klockan 08:26 -0600 skrev Alex Rousskov:
We may be able to provide better comments when we see the current code.
It does not have to be polished and ready for commit.
I see no reason to continue supporting now
much the same API.
Earlier TPROXY versions is quite different.
Yes, having clean support for multiple APIs is nice, and for Squid-3 we
should have TPROXY4 + Adrians FreeBSD thing.
If either one want's to spend time on making the older TPROXY support
fit in a such framework I won't object
On Wed, 2008-03-26 at 10:14 +1300, Amos Jeffries wrote:
Henrik Nordstrom wrote:
Revision 8905:
src/comm.cc: In function 'int comm_connect_addr(int, const IPAddress)':
src/comm.cc:1144: warning: passing NULL to non-pointer argument 2 of
'void* memset(void*, int, size_t)'
make[1]: ***
Revision 8905:
src/comm.cc: In function 'int comm_connect_addr(int, const IPAddress)':
src/comm.cc:1144: warning: passing NULL to non-pointer argument 2 of
'void* memset(void*, int, size_t)'
make[1]: *** [comm.lo] Error 1
Henrik Nordstrom wrote:
Revision 8905:
src/comm.cc: In function 'int comm_connect_addr(int, const IPAddress)':
src/comm.cc:1144: warning: passing NULL to non-pointer argument 2 of
'void* memset(void*, int, size_t)'
make[1]: *** [comm.lo] Error 1
What compiler are you using for this?
Amos
On Sun, 2008-03-23 at 18:29 +0900, Adrian Chadd wrote:
The real solution is a tree for offset lookups, and a linear walk of order
O(1) for subsequent sequential accesses.
Walking a tree is usually a cheap operation, unless the tree is wrongly
designed. You just need to remember the current
On Mon, 2008-03-24 at 11:25 +0100, Henrik Nordstrom wrote:
On Sun, 2008-03-23 at 18:29 +0900, Adrian Chadd wrote:
The real solution is a tree for offset lookups, and a linear walk of order
O(1) for subsequent sequential accesses.
Walking a tree is usually a cheap operation, unless the
On Fri, 2008-02-08 at 12:14 +0900, Adrian Chadd wrote:
Together they make a pretty tree. But every used piece is
eseentially
another new, memset, free.
Ah, and here you will have problems.
The members of that struct should probably be malloc, free, and not
new/delete. You're using
On Fri, 2008-02-08 at 12:14 +0900, Adrian Chadd wrote:
Together they make a pretty tree. But every used piece is
eseentially
another new, memset, free.
Ah, and here you will have problems.
The members of that struct should probably be malloc, free, and not
new/delete. You're using
Alex Rousskov wrote:
On Fri, 2008-02-08 at 15:52 +1300, Amos Jeffries wrote:
The second;
sockaddr_storage (as Husni uses, and Adrian mentioned) was created to
provide a better way of using sockaddr* so the sockaddr_in and
sockaddr_in6 bits could be read-written easily. But the big/litte
Amos Jeffries wrote:
Alex Rousskov wrote:
On Fri, 2008-02-08 at 15:52 +1300, Amos Jeffries wrote:
The second;
sockaddr_storage (as Husni uses, and Adrian mentioned) was created to
provide a better way of using sockaddr* so the sockaddr_in and
sockaddr_in6 bits could be read-written easily.
On Sat, Feb 09, 2008, Amos Jeffries wrote:
Correction: I did have online source that were somewhat confusing but
explained the behaviour a little. This seems to be saying what I
remember, http://www.kame.net/newsletter/19980604/
Today's rant:
The C standard libraries after about 1995
On Thu, 2008-02-07 at 12:21 +0900, Adrian Chadd wrote:
Well, I haven't removed the temporary malloc/free pair, whatever its
called;
I've just removed Amos' workaround in src/comm.cc so it doesn't leak
on my
system whilst I profile.
Still, this is one of those death of a thousand cuts
Uhm, the kernel won't be free'ing userland memory at all; it doesn't give
a rats how its managed.
You're probably confused with the library - the libc is fumbling with
all the struct addrinfo things.
Also, if the bug bugs you, create a temporary pointer and pass that in. ;)
Adrian
On Fri,
On Thu, 2008-02-07 at 14:08 +0900, Adrian Chadd wrote:
On Thu, Feb 07, 2008, Robert Collins wrote:
Still, this is one of those death of a thousand cuts method of
killing performance..
Right, I haven't seen the commit; care to mail the diff?
Which? I just looked at the places where
Have you tried running valgrind?
Also, wait. What exactly are you using addr_info for? Can you explain it
to me?
There's a netural sock addr size type - its called sockaddr_storage.
addr_info is for return results from hostname-ip queries..
Adrian
On Fri, Feb 08, 2008, Amos Jeffries wrote:
Uhm, the kernel won't be free'ing userland memory at all; it doesn't give
a rats how its managed.
You're probably confused with the library - the libc is fumbling with
all the struct addrinfo things.
Possibly. Once an external call is made I no longer care if its kernel or
library. Bad
On Thu, Feb 07, 2008, Robert Collins wrote:
Still, this is one of those death of a thousand cuts method of
killing performance..
Right, I haven't seen the commit; care to mail the diff?
Which? I just looked at the places where Amos is calling GetAddrInfo()
and FreeAddrInfo(); more then
Have you tried running valgrind?
Also, wait. What exactly are you using addr_info for? Can you explain it
to me?
The basics:
addrinfo* extends the neutral sockaddr* type ( union { sockaddr_in,
sockaddr_in6, sockaddr_storage} ) while adding the size values and
moving the flags and protocol
On Fri, Feb 08, 2008, Amos Jeffries wrote:
Try it. You will be horrified.
Why? Whats being trashed, AI, or AI-somemember?
If AI is being trashed, then just create a temporary pointer copy
of AI, use that in the socket call, and then throw it away.
if its trashing the memory -at- the AI rather
On Fri, Feb 08, 2008, Amos Jeffries wrote:
Try it. You will be horrified.
Why? Whats being trashed, AI, or AI-somemember?
AI-somemember.
If AI is being trashed, then just create a temporary pointer copy
of AI, use that in the socket call, and then throw it away.
if its trashing the
And which version of debian on which platform is showing the busted behaviour?
Adrian
On Fri, Feb 08, 2008, Amos Jeffries wrote:
On Thu, 2008-02-07 at 12:21 +0900, Adrian Chadd wrote:
Well, I haven't removed the temporary malloc/free pair, whatever its
called;
I've just removed
And which version of debian on which platform is showing the busted
behaviour?
Dell i386
Kernels 2.6.18-4 thru 2.6.22-2
libstdc6 with g++ 4.1 thru 4.3
All the debian setups I have had to test with basically since I first
found it.
Amos
On Fri, Feb 08, 2008, Amos Jeffries wrote:
On
On Fri, 2008-02-08 at 11:46 +1300, Amos Jeffries wrote:
The basics:
addrinfo* extends the neutral sockaddr* type ( union { sockaddr_in,
sockaddr_in6, sockaddr_storage} ) while adding the size values and
moving the flags and protocol details.
Hi Amos,
I understand that we need to
On Fri, 2008-02-08 at 11:46 +1300, Amos Jeffries wrote:
The basics:
addrinfo* extends the neutral sockaddr* type ( union { sockaddr_in,
sockaddr_in6, sockaddr_storage} ) while adding the size values and
moving the flags and protocol details.
Hi Amos,
I understand that we need to
can think of that does not break anything anywhere.
memset is needed there because I could not tell that the new/delete
_guaranteed_ pre-NULL'd memory and a single set bit in any unused fields
might cause a crash later.
With your deeper knowledge of the memory allocation in squid-3, feel free
On Fri, Feb 08, 2008, Amos Jeffries wrote:
sockaddr_storage (as Husni uses, and Adrian mentioned) was created to
provide a better way of using sockaddr* so the sockaddr_in and
sockaddr_in6 bits could be read-written easily. But the big/litte endian
problems between OS screwed up the
On Fri, 2008-02-08 at 15:52 +1300, Amos Jeffries wrote:
The second;
sockaddr_storage (as Husni uses, and Adrian mentioned) was created to
provide a better way of using sockaddr* so the sockaddr_in and
sockaddr_in6 bits could be read-written easily. But the big/litte endian
problems between
Amos, could you please poke the leak in IPAddress:GetAddrInfo a little?
I'll give it another try. But don't hold your breath too long on that one.
Did you see my note on it?
I tracked that leak backwards from two segfaults to the connect() system
call. Then I tracked the allocation from my init
On Thu, Feb 07, 2008, Amos Jeffries wrote:
Amos, could you please poke the leak in IPAddress:GetAddrInfo a little?
I'll give it another try. But don't hold your breath too long on that one.
Did you see my note on it?
I tracked that leak backwards from two segfaults to the connect() system
On Thu, Feb 07, 2008, Amos Jeffries wrote:
Amos, could you please poke the leak in IPAddress:GetAddrInfo a little?
I'll give it another try. But don't hold your breath too long on that one.
Why are you trying to allocate the structure on invocation of GetAddrInfo() ?
Wouldn't it be better
On Thu, Feb 07, 2008, Amos Jeffries wrote:
Amos, could you please poke the leak in IPAddress:GetAddrInfo a little?
I'll give it another try. But don't hold your breath too long on that one.
Did you see my note on it?
I tracked that leak backwards from two segfaults to the connect() system
On Thu, 2008-02-07 at 11:56 +0900, Adrian Chadd wrote:
Argh, this temporary malloc/free pair is peppered throughout the codebase!
Grr.
I've removed that hack, and things work fine for me. Ubuntu 7.01 here, x86_64.
There's a useful c++ thing called 'placement new' - its used when you
have
On Thu, Feb 07, 2008, Robert Collins wrote:
I've removed that hack, and things work fine for me. Ubuntu 7.01 here,
x86_64.
There's a useful c++ thing called 'placement new' - its used when you
have classes that you want to use on the stack, but still have tight
abstraction boundaries.
On Thu, 2008-02-07 at 12:21 +0900, Adrian Chadd wrote:
Well, I haven't removed the temporary malloc/free pair, whatever its
called;
I've just removed Amos' workaround in src/comm.cc so it doesn't leak
on my
system whilst I profile.
Still, this is one of those death of a thousand cuts
On Thu, Feb 07, 2008, Robert Collins wrote:
Still, this is one of those death of a thousand cuts method of
killing performance..
Right, I haven't seen the commit; care to mail the diff?
Which? I just looked at the places where Amos is calling GetAddrInfo()
and FreeAddrInfo(); more then
On Thu, Feb 07, 2008, Robert Collins wrote:
On Thu, 2008-02-07 at 14:08 +0900, Adrian Chadd wrote:
On Thu, Feb 07, 2008, Robert Collins wrote:
Still, this is one of those death of a thousand cuts method of
killing performance..
Right, I haven't seen the commit; care to mail
tis 2008-01-08 klockan 23:39 -0700 skrev Alex Rousskov:
The ICAPXaction::readBuf data member stores incoming headers. It is
initialized as follows:
readBuf.init(SQUID_TCP_SO_RCVBUF, SQUID_TCP_SO_RCVBUF);
Ok. So it should then be limited to TCP_SO_RCVBUF before seeing the same
problem.
On Wed, 2008-01-09 at 09:55 +0100, Henrik Nordström wrote:
tis 2008-01-08 klockan 23:39 -0700 skrev Alex Rousskov:
The ICAPXaction::readBuf data member stores incoming headers. It is
initialized as follows:
readBuf.init(SQUID_TCP_SO_RCVBUF, SQUID_TCP_SO_RCVBUF);
Ok. So it should
ons 2008-01-09 klockan 08:15 -0700 skrev Alex Rousskov:
My understanding is that you can replace the second SQUID_TCP_SO_RCVBUF
constant with a larger one to allow the buffer to grow. No other changes
should be needed except taking care of this assertion:
Yes, provided you actually try to
On Tue, 2008-01-08 at 03:47 +0100, Henrik Nordström wrote:
Squid-3 has lots of problems with response headers 4KB. (Bug #2001)
3.0.STABLE hangs and stops reading the response. Cleared by abort or
timeout only.
3.HEAD at least grows it's header receive buffer and continues to read
the data
Squid-3 has lots of problems with response headers 4KB. (Bug #2001)
3.0.STABLE hangs and stops reading the response. Cleared by abort or
timeout only.
3.HEAD at least grows it's header receive buffer and continues to read
the data and feed the response down the chain, but this then triggers
On tor, 2007-12-20 at 10:24 -0700, Alex Rousskov wrote:
On Tue, 2007-12-18 at 14:13 +0100, Henrik Nordstrom wrote:
On tis, 2007-12-18 at 23:32 +1300, Amos Jeffries wrote:
It really should not be for null.
The general syntax of cache_dir is
cache_dir type path option
path is
On tor, 2007-12-20 at 10:24 -0700, Alex Rousskov wrote:
On Tue, 2007-12-18 at 14:13 +0100, Henrik Nordstrom wrote:
On tis, 2007-12-18 at 23:32 +1300, Amos Jeffries wrote:
It really should not be for null.
The general syntax of cache_dir is
cache_dir type path option
path is
Hm, I'm not sure if this made it to squid-core so I'm reposting it
and to squid-dev this time.
I've tidied up the Squid-2, Squid-3 and Squid roadmap entries in
the Wiki:
http://wiki.squid-cache.org/RoadMap/
I'd like:
* Some feedback about the -2 and -3 roadmaps - especially since -2
Hm, I'm not sure if this made it to squid-core so I'm reposting it
and to squid-dev this time.
I've tidied up the Squid-2, Squid-3 and Squid roadmap entries in
the Wiki:
http://wiki.squid-cache.org/RoadMap/
I'd like:
* Some feedback about the -2 and -3 roadmaps - especially since -2
On Tue, 2007-10-02 at 14:47 +0800, Adrian Chadd wrote:
Hm, I'm not sure if this made it to squid-core so I'm reposting it
and to squid-dev this time.
I've tidied up the Squid-2, Squid-3 and Squid roadmap entries in
the Wiki:
http://wiki.squid-cache.org/RoadMap/
I'd like:
* Some
after. Remember the fiasco over squid-2.5 + (lots of patches
here) which people were running just to get modernish features?
Squid-2 should be looked at as an oppertunity to incrementally test
features out on a very larger userbase. Squid-3 and/or its children
should be where these features end up
, I'm not sure if this made it to squid-core so I'm reposting it
and to squid-dev this time.
I've tidied up the Squid-2, Squid-3 and Squid roadmap entries in
the Wiki:
http://wiki.squid-cache.org/RoadMap/
I'd like:
* Some feedback about the -2 and -3 roadmaps - especially since -2 is
mostly my
Hi Rob,
Robert Collins wrote:
Whats this summer you speak of?
I was speaking for Greek summer, the period of the year in Greece with
warm sunny days and better evenings, drinking wine, bears and ouzo near
the sea.
But, this summer was strange men, the sun looked sick behind the smoke
of
Hi Alex,
At 06.41 16/08/2007, Alex Rousskov wrote:
On Thu, 2007-08-16 at 09:20 +1200, Amos Jeffries wrote:
On Wed, 2007-08-15 at 09:58 +0200, Guido Serassio wrote:
Currently Squid is broken on all platforms without strtoll(), HP Tru64
is one.
I'm working on it, and I'm expecting to
On Fri, 2007-08-17 at 17:47 +0200, Guido Serassio wrote:
I propose to set as planned date for RC1 Wed 23/08.
I propose to release RC1 when strtoll() bug is fixed, provided no other
blockers are found by that time.
Regardless of the date, if you have a blocker that should be fixed,
please mark
Hi Alex,
At 18.50 17/08/2007, Alex Rousskov wrote:
On Fri, 2007-08-17 at 17:47 +0200, Guido Serassio wrote:
I propose to set as planned date for RC1 Wed 23/08.
I propose to release RC1 when strtoll() bug is fixed, provided no other
blockers are found by that time.
Now fixed.
I have just
On Fri, 2007-08-17 at 22:41 +0200, Guido Serassio wrote:
At 18.50 17/08/2007, Alex Rousskov wrote:
On Fri, 2007-08-17 at 17:47 +0200, Guido Serassio wrote:
I propose to set as planned date for RC1 Wed 23/08.
I propose to release RC1 when strtoll() bug is fixed, provided no other
Hi Alex,
At 00.14 18/08/2007, Alex Rousskov wrote:
- NetBSD 3.1
- OpenBSD 3.8
- HP Tru64 5.1
- Debian Linux 3.1
- Debian Linux 4.0
- SGI Irix 6.5.21
- Fedora Core 5
- Windows (Visual Studio 2005)
- Windows (MinGW)
Excellent!
BTW, do you actually have those physical/real machines or
Hi all,
Alex Rousskov wrote:
The primary idea behind RC1 is to bring in users who are ignoring PRE
releases because there were so many PREs. We need more testers than a
handful of folks running PREs on busy sites.
RC1 release to attract testers is a good idea. The only comment I have
is that
On Thu, 2007-08-16 at 11:59 +0300, Tsantilas Christos wrote:
Hi all,
Alex Rousskov wrote:
The primary idea behind RC1 is to bring in users who are ignoring PRE
releases because there were so many PREs. We need more testers than a
handful of folks running PREs on busy sites.
RC1
Robert Collins wrote:
On Thu, 2007-08-16 at 11:59 +0300, Tsantilas Christos wrote:
Hi all,
Alex Rousskov wrote:
The primary idea behind RC1 is to bring in users who are ignoring PRE
releases because there were so many PREs. We need more testers than a
handful of folks running PREs on busy
On Thu, 2007-08-16 at 11:59 +0300, Tsantilas Christos wrote:
RC1 release to attract testers is a good idea. The only comment I have
is that it is still summer and some of squid code submitters are still
in vacations so 1 or 2 developers get more load .
Maybe September is a better
+1... silly Northern hemisphere.
On 2007/08/16, at 7:21 PM, Robert Collins wrote:
On Thu, 2007-08-16 at 11:59 +0300, Tsantilas Christos wrote:
Hi all,
Alex Rousskov wrote:
The primary idea behind RC1 is to bring in users who are ignoring
PRE
releases because there were so many PREs. We
How long before the next pre or release candidate of squid-3 ?
Now that both of the blocker bugs are closed.
I submitted the last of the compile errors I can find today, it now builds
for both make check and make install.
Baring any of you others finding another I think we have reached step 2
Hi Adrian,
At 07.43 15/08/2007, Adrian Chadd wrote:
How long before the next pre or release candidate of squid-3 ?
Currently Squid is broken on all platforms without strtoll(), HP Tru64 is one.
I'm working on it, and I'm expecting to fix the problem and run some
tests on other platforms
On Wed, Aug 15, 2007, Guido Serassio wrote:
I think that we must wait for two weeks to see if the latest
large-objects changes are reasonably stable.
I was wondering about that. I thought 3.0 was reasonably
frozen.. anyway, I'll continue lurking.
Adrian
Hi Adrian,
At 10.04 15/08/2007, Adrian Chadd wrote:
On Wed, Aug 15, 2007, Guido Serassio wrote:
I think that we must wait for two weeks to see if the latest
large-objects changes are reasonably stable.
I was wondering about that. I thought 3.0 was reasonably
frozen.. anyway, I'll continue
On Wed, 2007-08-15 at 09:58 +0200, Guido Serassio wrote:
Currently Squid is broken on all platforms without strtoll(), HP Tru64 is one.
I'm working on it, and I'm expecting to fix the problem and run some
tests on other platforms (Irix, NetBSD and OpenBSD) within the
incoming weekend.
On Wed, 2007-08-15 at 09:58 +0200, Guido Serassio wrote:
Currently Squid is broken on all platforms without strtoll(), HP Tru64
is one.
I'm working on it, and I'm expecting to fix the problem and run some
tests on other platforms (Irix, NetBSD and OpenBSD) within the
incoming weekend.
On Thu, 2007-08-16 at 09:20 +1200, Amos Jeffries wrote:
On Wed, 2007-08-15 at 09:58 +0200, Guido Serassio wrote:
Currently Squid is broken on all platforms without strtoll(), HP Tru64
is one.
I'm working on it, and I'm expecting to fix the problem and run some
tests on other platforms
able to understand what a piece of code of
Squid 2 does.
Now I feel really frustrated when I can't understand why a single
line of code of Squid 3 doesn't build or why your patch works :-(
I have also tried to learn C++ by myself, but with little result
because I don't have enough time
years?
New technologies come again and again ...
Now I feel really frustrated when I can't understand why a single line
of code of Squid 3 doesn't build or why your patch works :-(
The major problem you may have is that c++ compilers some times return
error messages which looks completely
Henrik, but I was always able to understand what a piece of code of
Squid 2 does.
Now I feel really frustrated when I can't understand why a single
line of code of Squid 3 doesn't build or why your patch works :-(
I have also tried to learn C++ by myself, but with little result
because I
doxygen helps a lot to decipher unknown code. Without them
reading and understanding complex C++ code is a nightmare.
But this is also where the powers of C++ lies. The abstraction levels do
allows for clean code to be done easier than in for example C.
The Squid-3 code is currently a bit messy with 4
.
Tools like doxygen helps a lot to decipher unknown code. Without them
reading and understanding complex C++ code is a nightmare.
But this is also where the powers of C++ lies. The abstraction levels do
allows for clean code to be done easier than in for example C.
The Squid-3 code is currently
How long before the next pre or release candidate of squid-3 ?
Adrian
On Sat, 2007-08-11 at 23:06 +0200, Serassio Guido wrote:
Hi,
Trying to build the current Squid 3 source using Visual Studio 2005
on Windows, I get the following error.
Any C++ suggestion ?
Compiling...
mem.cc
c:\work\nt-3.0\src\StoreEntryStream.h(119) : error C2512:
'std
Serassio Guido wrote:
Hi,
Trying to build the current Squid 3 source using Visual Studio 2005 on
Windows, I get the following error.
Any C++ suggestion ?
hehe, StoreEntryStream, again.
Alex just fixed the last bug in there for me, he may have better grasp
of it at the moment.
Here
Hi Amos,
At 12.14 12/08/2007, Amos Jeffries wrote:
Serassio Guido wrote:
Hi,
Trying to build the current Squid 3 source using Visual Studio 2005
on Windows, I get the following error.
Any C++ suggestion ?
hehe, StoreEntryStream, again.
Alex just fixed the last bug in there for me, he may
Henrik Nordstrom wrote:
mån 2007-05-28 klockan 23:17 +0800 skrev Adrian Chadd:
Personally, I think we've all learnt a bit from this experience, and
there's a clearer path forward for tidying up the string (ab)uses going
on in the codebase.
I'm all for calling this a lesson learnt, backing it
Hi guys,
Could we please make a decision about SqString? I'm leaning towards
backing it out for now, releasing Squid-3, and then doing a phased
introduction post squid-3 - starting with just accessor method
changes..
Adrian
Adrian Chadd wrote:
Hi guys,
Could we please make a decision about SqString? I'm leaning towards
backing it out for now, releasing Squid-3, and then doing a phased
introduction post squid-3 - starting with just accessor method
changes..
Adrian
I was waiting on Alex (or anyones) response
On Tue, May 29, 2007, Amos Jeffries wrote:
I was waiting on Alex (or anyones) response to my last email, before
going either way.
well, count this as a reply to your last email. :)
partial backout: proposal (no responses)
full backout: 3 for, 2 wavering with doubts, 1 abstention.
Doing my usual run of squid checking:
471 0.9703 squidxxfree
486 1.0012 squidHttpHeader::clean()
795 1.6377 squidACLChecklist::fastCheck()
1250 2.5750 squidxmalloc
1392 2.8676
.. hm, the global info:
CPU: P4 / Xeon, speed
*) [self]
3321 0.9255 squidMemPool::push(void*)
.. definitely should look into trying to sort out memory allocation overhead
and what can/can't be bzero'ed post squid-3 release. Being able to get back 20%
of the CPU runtime from memset would be very very shiny.
Adrian
/diffs/2007-05-19-squid3-ipfw-transparent.diff
I'll commit this tomorrow night if noone has any complaints.
(All of this means I can get squid-3 + ipfw + freebsd6 + wccpv2 working.)
Adrian
Hi Adrian:
I've created a SF branch to do my logging helper stuff in squid-3 -
squid3_logdaemon .
So far I'm just concentrating on breaking out the existing two methods, being
syslog and (somewhat) blocking writes.
I'll port my logfile daemon and the Wikipedia UDP logging modules over once
On Sun, 13 May 2007, Henrik Nordstrom wrote:
s??n 2007-05-13 klockan 10:39 +0200 skrev Guido Serassio:
The Squid 3 download page is stuck at 9 May, may be related to PRE6 release.
Checking... yes. The -CVS part of the version tag should not be removed.
It's removed automatically
mån 2007-05-14 klockan 13:53 -0600 skrev Duane Wessels:
/path/to/squid-3/mkrelease.sh 3.0.PRE6
/path/to/www.squid-cache.org/Versions/v3/3.0/
I was going to see about updating release notes and such.
You need to do that before you set the CVS tag...
I updated the web page and copied
Hi,
The Squid 3 download page is stuck at 9 May, may be related to PRE6 release.
Regards
Guido
-
Guido Serassio
Acme Consulting S.r.l. - Microsoft Certified Partner
Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY
Tel
sön 2007-05-13 klockan 10:39 +0200 skrev Guido Serassio:
The Squid 3 download page is stuck at 9 May, may be related to PRE6 release.
Checking... yes. The -CVS part of the version tag should not be removed.
It's removed automatically by the mkrelease script. It's there so we
know when people
tor 2007-04-12 klockan 20:31 +0200 skrev Guido Serassio:
Here I think that a methodical comparison between 2.6 and 3.0 is needed.
Not so sure. Find it much more important Squid-3 is stable than feature
complete wrt 2.6.
Probably there are a lot of not so big changes missing in 3.0.
Very
tor 2007-04-12 klockan 13:19 -0600 skrev Alex Rousskov:
IMO, if we can support enough directives to accommodate 51% of current
Squid2 users, that is enough.
More importantly, thanks to the new major features of Squid-3 such as a
good ICAP client we might attract new users again, not only
is then applied to Squid-3 as well.
- HEAD always kept open for new reasonably stable stuff, allowing
development to progress natuarlly without having completed stuff
bitrotting in some seldom looked at development branch.
- If problems is seen in HEAD they get fixed, or the changes causing the
problems
failed
Autotool bootstrapping failed. You will need to investigate and correct
before you can develop on this source tree
On Fri, 16 Mar 2007 20:26:03 +0100
Henrik Nordstrom [EMAIL PROTECTED] wrote:
tor 2007-03-15 klockan 13:26 +0700 skrev Wahyu:
I want to try the gzip content encode with squid
here's some error after i did the bootstrap.sh:
Bootstrapping
/usr/share/aclocal/pth.m4:43: warning: underquoted definition of
_AC_PTH_ERROR run info '(automake)Extending aclocal'
or see
http://sources.redhat.com/automake/automake.html#Extending-aclocal
/usr/share/aclocal/pth.m4:55:
tor 2007-03-15 klockan 13:26 +0700 skrev Wahyu:
I want to try the gzip content encode with squid 3 but i got problem
with that, patch and make are success, but when i'm running the
squid i got this error:
Starting proxy server: 2007/03/15 12:57:53| parseConfigFile:
'squid.conf' line 294
Hi,
I want to try the gzip content encode with squid 3 but i got problem
with that, patch and make are success, but when i'm running the
squid i got this error:
Starting proxy server: 2007/03/15 12:57:53| parseConfigFile:
'squid.conf' line 294 unrecognized: 'negotiate_ce_access allow all'
2007
Squid 3 HEAD and includes 4 changes I would
like to have when working with webwasher/squid systems.
A.) ICAPServiceRep::TheSessionFailureLimit set through squid.conf
B.) ICAPServiceRep delay for a down service set through squid.conf
C.) Instead of hardcoding the Header used to transfer
schrieb Alex Rousskov unter
[EMAIL PROTECTED]:
On Mon, 2006-12-04 at 12:57 +0100, Axel Westerhold wrote:
Hi everyone,
Second try this time hopefully complete.
This is again patched against Squid 3 HEAD and includes 4 changes
I would
like to have when working with webwasher/squid
101 - 200 of 317 matches
Mail list logo
