Should we back out SqString for now until the implicit cast issues have
been analyzed in more detail, or try fixing it somehow for the 3.0
release?
http://www.squid-cache.org/bugs/show_bug.cgi?id=1970
My vote is to defer the SqString change to 3.1, or at least after 3.0
has been branched from
I have done two patches in order to synchronize the language and
formatting of the cf.data.pre file in the 2.6 and 3.0 releases.
This is intended to see if this is the correct way to go ahead with this
files synchronizing.
Thanks
Emilio C.
--- squid-2.6.STABLE13/src/cf.data.pre 2007-05-17
tor 2007-05-24 klockan 12:26 +0200 skrev Emilio Casbas:
I have done two patches in order to synchronize the language and
formatting of the cf.data.pre file in the 2.6 and 3.0 releases.
This is intended to see if this is the correct way to go ahead with this
files synchronizing.
Looks good.
On Thu, 2007-05-24 at 11:19 +0200, Henrik Nordstrom wrote:
Should we back out SqString for now until the implicit cast issues have
been analyzed in more detail, or try fixing it somehow for the 3.0
release?
http://www.squid-cache.org/bugs/show_bug.cgi?id=1970
My vote is to defer the
Hi there,
Before SqString patch applied, squid3 looked stable, I had days to see a
problem.
The SqString had unpredicted effects in squid3 like the bug 1970. And
maybe there are other issues not appeared yet. It was not enough
analyzed before applied.
Regards,
Christos
PS. Last
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
On Thu, 2007-05-24 at 11:19 +0200, Henrik Nordstrom wrote:
Should we back out SqString for now until the implicit cast issues have
been analyzed in more detail, or try fixing it somehow for the 3.0
release?
http://www.squid-cache.org/bugs/show_bug.cgi?id=1970
My vote is to defer the
On Thu, May 24, 2007, Alex Rousskov wrote:
I still think SqString API changes should not be in 3.0, but I do not
have a strong opinion and do not want to be the one backing them out.
We could adopt a middle-ground solution. The changes limited to renaming
String methods to match std::string
On Thu, May 24, 2007, Adrian Chadd wrote:
.. hm, the global info:
.. and just now, after fixing some local connectivity issues at home which
prevented the hammering actually .. hammering. I've also removed the kernel
profiling time just so the user space percentages are very visible.
CPU: P4
Dear Alex,
Alex Rousskov wrote:
Sounds like bug #1633 to me, but I do not know much about SSL-related
code. Anybody in-the-know care to comment?
Just notice that Squid is NOT built with SSL libraries. I never thought
it was necessary (and most HTTPS stuff works fine).
Which version did
On Thu, 2007-05-24 at 16:58 +0200, Emmanuel Eyer wrote:
It still crashes randomly, but at most once or twice a day. Thus now the
HTTPS issue became visible (or popped up).
Please consider filing bug reports for all crashes we do not know about.
Thank you,
Alex.
On Wed, May 23, 2007, Mahesh Govindappa wrote:
i wrote a simple program just for checking purpose.
#include stdio.h
#include string.h
int main()
{
char buf[8192];
fgets(buf, 256, stdin);
FILE *fp;
fp=fopen(/etc/test.txt, w);
fprintf(fp,%s, buf);
fclose(fp);
printf(OK\n);
}
13 matches
Mail list logo
