On 2020-08-31 16:30, Kurt Jaeger wrote:
Hi!
I see Squid 4.13 was released 8 days ago: it's "strongly suggested"
everyone updates, as it fixes "serious" security issues.
I don't see it coming in the port tree and neither in the pkg audit
vulnerability databa
> On 31. Aug 2020, at 16:31, Kurt Jaeger wrote:
>
> Hi!
>
>> I see Squid 4.13 was released 8 days ago: it's "strongly suggested"
>> everyone updates, as it fixes "serious" security issues.
>>
>> I don't see it coming in th
Hi!
> I see Squid 4.13 was released 8 days ago: it's "strongly suggested"
> everyone updates, as it fixes "serious" security issues.
>
> I don't see it coming in the port tree and neither in the pkg audit
> vulnerability database.
https://bugs.freeb
Hello.
I see Squid 4.13 was released 8 days ago: it's "strongly suggested"
everyone updates, as it fixes "serious" security issues.
I don't see it coming in the port tree and neither in the pkg audit
vulnerability database.
If you already knew, pleas
:
> Hi!
>
> > Could anybody take a look at these PRs and commit them if possible?
>
> Done.
>
> --
> p...@opsec.eu+49 171 3101372Now what ?
>
Highly appreciate!
>
___
freebsd-ports@freebsd.org mailing list
https://lists.
Hi!
> Could anybody take a look at these PRs and commit them if possible?
Done.
--
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-por
Hi,
Could anybody take a look at these PRs and commit them if possible?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246355 - www/squid-devel:
add patch to fix kerberos_ldap_group helper
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246410 - www/squid:
pinger doesn't start after r5
On Tue, Apr 26, 2016 at 1:31 AM, Pavel Timofeev wrote:
> 2016-04-26 1:32 GMT+03:00 Nick Rogers :
> > Hello,
> >
> > I just recompiled my www/squid port to the latest 3.5.17 version. Prior
> to
> > this I was running 3.5.14. I immediately noticed that my transparen
On 04/26/16 10:41, Franco Fichtner wrote:
> Hi,
>
>> On 26 Apr 2016, at 10:31 AM, Pavel Timofeev wrote:
>>
>> 2016-04-26 1:32 GMT+03:00 Nick Rogers :
>>>
>>> I was able to fix my issue by recompiling without the TP_IP and TP_IPF
>>> options, but I believe more thought/discussion should be given t
Hi,
> On 26 Apr 2016, at 10:31 AM, Pavel Timofeev wrote:
>
> 2016-04-26 1:32 GMT+03:00 Nick Rogers :
>>
>> I was able to fix my issue by recompiling without the TP_IP and TP_IPF
>> options, but I believe more thought/discussion should be given to all the
>> new options that are now enabled by d
2016-04-26 1:32 GMT+03:00 Nick Rogers :
> Hello,
>
> I just recompiled my www/squid port to the latest 3.5.17 version. Prior to
> this I was running 3.5.14. I immediately noticed that my transparent proxy
> setup via PF was broken and throwing a "Forwarding loop detected&
Hello,
I just recompiled my www/squid port to the latest 3.5.17 version. Prior to
this I was running 3.5.14. I immediately noticed that my transparent proxy
setup via PF was broken and throwing a "Forwarding loop detected" error in
the logs.
I then noticed the following recent co
Hi!
> Could anybody, please, take care of this one
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207901?
Done. Still needs MFH, I'm not sure I have the time for it.
--
p...@opsec.eu+49 171 3101372 4 years to go !
Good day!
Could anybody, please, take care of this one
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207901?
Thank you!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail t
2016-03-31 22:05 GMT+03:00 Kurt Jaeger :
> Hi!
>
>> > > Can anybody take a look at
>> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208290?
>> > > Thanks!
>> >
>> > I'd like it to be committed before new quarter branch is made.
>>
>> @work
>
> Done, thanks for the reminder!
>
Thanks a lot!
Hi!
> > > Can anybody take a look at
> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208290?
> > > Thanks!
> >
> > I'd like it to be committed before new quarter branch is made.
>
> @work
Done, thanks for the reminder!
--
p...@opsec.eu+49 171 3101372
Hi!
> > Can anybody take a look at
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208290?
> > Thanks!
>
> I'd like it to be committed before new quarter branch is made.
@work
--
p...@opsec.eu+49 171 3101372 4 years to go !
2016-03-30 15:51 GMT+03:00 Pavel Timofeev :
> Hello!
> Can anybody take a look at
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208290?
> Thanks!
I'd like it to be committed before new quarter branch is made.
___
freebsd-ports@freebsd.org mailing l
Hello!
Can anybody take a look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208290?
Thanks!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubsc
On 6/12/2015 8:44 PM, Pavel Timofeev wrote:
> Hi!
> I'm a maintainer of squid port and I'd like to ask you about default
> squid options turned on by default.
> Squid 4 is in release candidate stage now and we already have an
> initial port for it here
> https
t;distributions" require? Yes, to the
extent that the options that they require, function correctly; particularly
when the requirements are mutually exclusive.
To your point about kerberos, I build ports against the heimdal port, and
the package content is correctly linked,
Hi!
I'm a maintainer of squid port and I'd like to ask you about default
squid options turned on by default.
Squid 4 is in release candidate stage now and we already have an
initial port for it here
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203860.
So, how do you think, wh
On Tue, Jun 30, 2015 at 2:36 PM, Nick Rogers wrote:
>
>
> On Tue, Jun 30, 2015 at 11:54 AM, Dimitry Andric wrote:
>
>> On 30 Jun 2015, at 18:48, Nick Rogers wrote:
>> ...
>> > I am experiencing an issue with squid 3.5.5 and FreeBSD 10.1 where
>> > t
On Tue, Jun 30, 2015 at 11:54 AM, Dimitry Andric wrote:
> On 30 Jun 2015, at 18:48, Nick Rogers wrote:
> ...
> > I am experiencing an issue with squid 3.5.5 and FreeBSD 10.1 where
> > tcp_outgoing_address correctly rewrites the source address of outgoing
> > packet
On 30 Jun 2015, at 18:48, Nick Rogers wrote:
...
> I am experiencing an issue with squid 3.5.5 and FreeBSD 10.1 where
> tcp_outgoing_address correctly rewrites the source address of outgoing
> packets, but fails to bind the socket to the correct interface.
How do you arrive at this c
Hello,
I am experiencing an issue with squid 3.5.5 and FreeBSD 10.1 where
tcp_outgoing_address correctly rewrites the source address of outgoing
packets, but fails to bind the socket to the correct interface. I've been
using this kind of setup/configuration for quite some time (since the
Hi!
> I build-tested it and it looks fine. There is still the
> issue with building it with the base kerberos on a host where
> one of the kerberos ports is installed. For those cases, use
> poudriere.
>
> I will update the port in approx. 24 hours if there are no reports
> of things breaking. So
On Mon, 13 Apr 2015, 20:28 +0200, Kurt Jaeger wrote:
> > The squid35 port has been updated to lastest 3.5.3 release.
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089
> > This time it's a patch for the existing www/squid.
> > Please, test it and write a fe
Hi!
> The squid35 port has been updated to lastest 3.5.3 release.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089
> This time it's a patch for the existing www/squid.
> Please, test it and write a feed back!
>
> IMO it's ready to import.
I build-tested it
Hi all!
The squid35 port has been updated to lastest 3.5.3 release.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089
This time it's a patch for the existing www/squid.
Please, test it and write a feed back!
IMO it's ready to import.
2015-03-20 11:43 GMT+03:00 Pavel Timofeev
Hello!
The new shar file squid35-20.03.15.shar was uploaded today. Look at
this PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089.
You can find my comments about progress there.
I'm asking people who is using www/squid: please, test it as much as possible!
P.S. It's a new
Hi! I've just made a small update there
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089
2015-02-28 15:30 GMT+03:00 Pavel Timofeev :
> Ok, I'll do my best.
>
> 2015-02-28 14:08 GMT+03:00 Kurt Jaeger :
>> Hi!
>>
>>> > Just in case, I uploaded it here https://yadi.sk/d/EcRxwc6BevgDc
>>>
>>>
Well, in general, I don't mind, but I'm afraid I'm not a skillful person.
2015-02-28 11:00 GMT+03:00 Kurt Jaeger :
> Hi!
>
>> > Sorry, my fault. Not a patch for existing port, but a shar file to
>> > create new port, which was attached to original message.
>> > Just in case, I uploaded it here htt
Ok, I'll do my best.
2015-02-28 14:08 GMT+03:00 Kurt Jaeger :
> Hi!
>
>> > Just in case, I uploaded it here https://yadi.sk/d/EcRxwc6BevgDc
>>
>> I've created
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089
>>
>> with that shar and I'm build-testing it right now.
>
> build testing:
Hi!
> > Just in case, I uploaded it here https://yadi.sk/d/EcRxwc6BevgDc
>
> I've created
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089
>
> with that shar and I'm build-testing it right now.
build testing: works on 10.1a, fails on 9.3a, 8.4i.
poudriere build logs can be found
Hi!
> > Sorry, my fault. Not a patch for existing port, but a shar file to
> > create new port, which was attached to original message.
> > Just in case, I uploaded it here https://yadi.sk/d/EcRxwc6BevgDc
>
> I've created
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089
>
> with th
Hi!
> Sorry, my fault. Not a patch for existing port, but a shar file to
> create new port, which was attached to original message.
> Just in case, I uploaded it here https://yadi.sk/d/EcRxwc6BevgDc
I've created
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089
with that shar and I'm bu
Hi Pavel,
When we had 3 unmaintained squid ports, the idea was the get down to
one, www/squid. The only reason www/squid33 is still in ports is
because you requested an extension on it's removal due to the FreeBSD
10.1 RC issues.
I personally don't want to see that contractio
>> I created an initial port for squid-3.5.
>> It's squid-3.5.2.
>>
>> Release notes for 3.5 branch are here
>> http://wiki.squid-cache.org/Squid-3.5.
>>
>> Port based on www/squid.
>>
>> Existing problems with some options:
>> ECAP - ma
On 2015-02-27 07:01, Pavel Timofeev wrote:
Hi!
I created an initial port for squid-3.5.
It's squid-3.5.2.
Release notes for 3.5 branch are here
http://wiki.squid-cache.org/Squid-3.5.
Port based on www/squid.
Existing problems with some options:
ECAP - marked as broken for now, because
There is no maintainer for squid ports, so I guess there is no plans.
IMO www/squid33 should be removed, no reason to keep it in ports.
www/squid should be moved to www/squid34 for some time (~3 or more months)
www/squid should be upgraded to 3.5 branch.
Meanwhile, I tried to create a port for
Hi!
I created an initial port for squid-3.5.
It's squid-3.5.2.
Release notes for 3.5 branch are here http://wiki.squid-cache.org/Squid-3.5.
Port based on www/squid.
Existing problems with some options:
ECAP - marked as broken for now, because squid-3.5 needs eCAP version
1.0 which is n
On Mon, Feb 23, 2015 at 5:41 PM, Dewayne Geraghty
wrote:
> Thank you so much for posting this link! Merging r275456 and r275502
> from stable/10 to my releng/10.1 src tree and rebuilding and installing
> the kernel, means that I can once again manage squid 3.4.n via the rc.d
> scrip
hu, 19 Feb 2015 21:23:15 -0500
>>>> Robert Simmons wrote:
>>>>
>>>>
>>>> That is true. It looks like an update to both 3.5 and 3.4 were
>>>>> released on the same day. How about dropping www/squid33 and
>>>>> creating a www/squid34
;>
>>> That is true. It looks like an update to both 3.5 and 3.4 were
>>>> released on the same day. How about dropping www/squid33 and
>>>> creating a www/squid34 port. Then updating the www/squid port to
>>>> 3.5.2.
>>>>
>>> I wo
www/squid34 port. Then updating the www/squid port to
3.5.2.
I would say this is a bad idea, as squid 3.5 does not work on FreeBSD
10.1 with GENERIC kernel. Furthermore, it won't be fixed with
binary patches (ie. until 10.2 or 11.0).
I think www/squid should be recommended squid versio
ating a www/squid34 port. Then updating the www/squid port to
> > 3.5.2.
>
> I would say this is a bad idea, as squid 3.5 does not work on FreeBSD
> 10.1 with GENERIC kernel. Furthermore, it won't be fixed with
> binary patches (ie. until 10.2 or 11.0).
>
> I think www/sq
> a www/squid34 port. Then updating the www/squid port to 3.5.2.
>
> I would say this is a bad idea, as squid 3.5 does not work on FreeBSD
> 10.1 with GENERIC kernel. Furthermore, it won't be fixed with
> binary patches (ie. until 10.2 or 11.0).
> I think www/squid should be
On Thu, 19 Feb 2015 21:23:15 -0500
Robert Simmons wrote:
> That is true. It looks like an update to both 3.5 and 3.4 were
> released on the same day. How about dropping www/squid33 and creating
> a www/squid34 port. Then updating the www/squid port to 3.5.2.
I would say this is a bad
On Thu, Feb 19, 2015 at 7:13 PM, Nick Rogers wrote:
> On Thu, Feb 19, 2015 at 6:46 AM, Robert Simmons wrote:
>>
>> According to the Squid website:
>> "Provided for archival purposes only. Not intended for general use in
>> new installations."
>> This
On Thu, Feb 19, 2015 at 6:46 AM, Robert Simmons wrote:
> According to the Squid website:
> "Provided for archival purposes only. Not intended for general use in
> new installations."
> This is marking all versions of Squid except 3.5
> http://www.squid-cache.org/Versio
According to the Squid website:
"Provided for archival purposes only. Not intended for general use in
new installations."
This is marking all versions of Squid except 3.5
http://www.squid-cache.org/Versions/
I would recommend removing all the older unsupported versions except 3.5.
On W
It seems that squid 3.5 is becoming the latest recommended production
quality version. Squid 3.4.12 and 3.5.2 were just released today. What is
everyones thought (or the maintainers plan) on moving the www/squid port
from 3.4 to 3.5?
It looks like the www/squid33 port has been kept around past
On Mon, Feb 2, 2015 at 11:00 AM, Nick Rogers wrote:
>
>
> On Fri, Jan 30, 2015 at 8:51 PM, Kevin Oberman
> wrote:
>
>> On Wed, Jan 28, 2015 at 6:58 AM, Dr. Peter Voigt wrote:
>>
>> > On Tue, 27 Jan 2015 11:51:51 +0100
>> > Marko Cupać wrote:
>> >
>> > > On Tue, 27 Jan 2015 07:11:10 +
>> >
On Fri, Jan 30, 2015 at 8:51 PM, Kevin Oberman wrote:
> On Wed, Jan 28, 2015 at 6:58 AM, Dr. Peter Voigt wrote:
>
> > On Tue, 27 Jan 2015 11:51:51 +0100
> > Marko Cupać wrote:
> >
> > > On Tue, 27 Jan 2015 07:11:10 +
> > > Matthew Seaman wrote:
> > >
> > > > On 2015/01/27 03:52, Kurt Jaege
On Wed, Jan 28, 2015 at 6:58 AM, Dr. Peter Voigt wrote:
> On Tue, 27 Jan 2015 11:51:51 +0100
> Marko Cupać wrote:
>
> > On Tue, 27 Jan 2015 07:11:10 +
> > Matthew Seaman wrote:
> >
> > > On 2015/01/27 03:52, Kurt Jaeger wrote:
> > > > Doesn't installing a custom kernel break freebsd-update
On Tue, 27 Jan 2015 11:51:51 +0100
Marko Cupać wrote:
> On Tue, 27 Jan 2015 07:11:10 +
> Matthew Seaman wrote:
>
> > On 2015/01/27 03:52, Kurt Jaeger wrote:
> > > Doesn't installing a custom kernel break freebsd-update ?
> >
> > No. freebsd-update has always supported using a custom kerne
On 2015/01/27 10:51, Marko Cupać wrote:
> I guess theoretically it is possible to make "kernel build server" which
> will build custom kernel for distribution to other servers. I am just
> not sure how will RELEASE userland tolerate STABLE kernel.
You can use the 10.1-RELEASE sources and apply the
On Tue, 27 Jan 2015 07:11:10 +
Matthew Seaman wrote:
> On 2015/01/27 03:52, Kurt Jaeger wrote:
> > Doesn't installing a custom kernel break freebsd-update ?
>
> No. freebsd-update has always supported using a custom kernel. It
> helps if you name your kernel something other than GENERIC, w
On 2015/01/27 03:52, Kurt Jaeger wrote:
> Doesn't installing a custom kernel break freebsd-update ?
No. freebsd-update has always supported using a custom kernel. It
helps if you name your kernel something other than GENERIC, which you do
by creating a modofoed kernel config file in /usr/src/sys
ode for VMS. I
am a system admin, either full or part time for at least 35 years, though,
so I am more comfortable than the average user. But the average user is not
installing and configuring squid, either.
It's a simple process and, as always when a new kernel is installed, the
old one is sa
Hi!
> As far as patching, it is really pretty easy and requires no special skills
> or knowledge.
>
> 1. Download the two patches as ~/A.patch and ~/B.patch
[...]
Doesn't installing a custom kernel break freebsd-update ?
--
p...@opsec.eu+49 171 3101372 5 yea
2014-08-27
>>> - squid33 has been scheduled for expiration on 2015-01-31, but was
>>> extended to 2015-05-31 because of ntlm_auth issue in squid34
>>> - squid34 does not run on 10.1-RELEASE-pX
>>> - 10.2-RELEASE is not likely to be before 2015-05-31
>>>
4
> > - squid34 does not run on 10.1-RELEASE-pX
> > - 10.2-RELEASE is not likely to be before 2015-05-31
> >
> > Which means that pkg installs of latest squid (www/squid34) will be
> > useless on latest FreeBSD release (10.1-RELEASE) for a long time.
> >
On Tue, 27 Jan 2015, 00:29 +0900, Yasuhiro KIMURA wrote:
>
> Yes, this is bug. But it is bug of 10.1-RELEASE rather than squid.
> See following bug report:
>
> Bug 195802 - www/squid restarts after shutdown and dumps core
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=19
se on 2014-08-27
> - squid33 has been scheduled for expiration on 2015-01-31, but was
> extended to 2015-05-31 because of ntlm_auth issue in squid34
> - squid34 does not run on 10.1-RELEASE-pX
> - 10.2-RELEASE is not likely to be before 2015-05-31
>
> Which means that pkg insta
on 2014-08-27
> - squid33 has been scheduled for expiration on 2015-01-31, but was
> extended to 2015-05-31 because of ntlm_auth issue in squid34
> - squid34 does not run on 10.1-RELEASE-pX
> - 10.2-RELEASE is not likely to be before 2015-05-31
>
> Which means that pkg installs of
lm_auth issue in squid34
- squid34 does not run on 10.1-RELEASE-pX
- 10.2-RELEASE is not likely to be before 2015-05-31
Which means that pkg installs of latest squid (www/squid34) will be
useless on latest FreeBSD release (10.1-RELEASE) for a long time.
> They will, however, be in the next rel
On 01/26/15 16:05, Yasuhiro KIMURA wrote:
> https://svnweb.freebsd.org/base/stable/10/sys/kern/kern_sig.c?view=patch&r1=275456&r2=275455&pathrev=275456
> https://svnweb.freebsd.org/base/stable/10/sys/kern/kern_sig.c?view=patch&r1=275502&r2=275501&pathrev=275502
>
> As URLs suggest, they are patch
From: Marko Cupać
Subject: Re: www/squid does not shutdown via rc
Date: Mon, 26 Jan 2015 16:39:34 +0100
> Thank you for your reply. Where can those fixes be found?
It is in the svn repository of base system. Revisions are r275456 and
r275502. You can download them from following URLs.
ht
On Tue, 27 Jan 2015 00:29:19 +0900 (JST)
Yasuhiro KIMURA wrote:
> From: Marko Cupać
> Subject: www/squid does not shutdown via rc
> Date: Mon, 26 Jan 2015 15:24:33 +0100
>
> > Could it be that I am doing something wrong or is this a bug?
>
> Yes, this is bug. But i
From: Marko Cupać
Subject: www/squid does not shutdown via rc
Date: Mon, 26 Jan 2015 15:24:33 +0100
> Could it be that I am doing something wrong or is this a bug?
Yes, this is bug. But it is bug of 10.1-RELEASE rather than squid.
See following bug report:
Bug 195802 - www/squid restarts af
Hi,
I am building new proxy server based on FreeBSD 10.1-RELEASE and latest
squid from ports (squid-3.4.11).
Squid starts and works ok when testing from single client, but it does
not shutdown correctly through rc script.
Starting situation: squid is not started, no pid dir and file in /var/run
Hello
squid-3.4.10_2 after installation, do not work directives from config at
assembly of the package is not found where they ask to include support in the
assembly,
thank you.
+++ --enable-http-violations
log:
2015/01/03 20:02:08| Processing: request_header_access X-Forwarded-For deny all
After my recent upgrade to 10.1-RELEASE (amd64) have have rebuilt all
ports. At the end of this proces I rebooted the machine and saw a
pid (squid), uid 100: exited on signal 6 (core dumped)
message in the kernel log. This behavior of Squid is reproducible on
every shutdown of Squid, e.g
On Wed, Oct 15, 2014 at 09:11:44PM +0200, Dimitry Andric wrote:
> Hi,
>
> Since http://bazaar.launchpad.net/~squid/squid/3-trunk/revision/12842,
> Squid's configure script defaults to -march=native, if the flag is
> supported by the compiler. And this even *overrides
Hi,
Since http://bazaar.launchpad.net/~squid/squid/3-trunk/revision/12842,
Squid's configure script defaults to -march=native, if the flag is
supported by the compiler. And this even *overrides* your own specified
CPUTYPE or -march= flag! So I personally experienced Squid 3.4 crashing
on a
FYI (I'm not on this list):
A patch might no longer be needed.
- Forwarded message -
Date: Wed, 15 Oct 2014 18:03:04 +0100
From: "Craig R. Skinner"
To: po...@openbsd.org
Subject: Re: Squid -vs- IPv6
User-Agent: Mutt/1.5.22 (2013-10-16)
On 2014-05-19 Mon 12:01 PM |, C
I added my observations via forward to the freebsd ports list since that is
the listed maintainer for squid.
Brian
On Sep 25, 2014 10:11 PM, "Victor Sudakov" wrote:
> Dewayne Geraghty wrote:
> > >>
> > >> squid-3.4.8_1 seems to be leaking memory heavily
Dewayne Geraghty wrote:
> >>
> >> squid-3.4.8_1 seems to be leaking memory heavily. Its SIZE and RES are
> >> growing several MB per minute until eventually swapping begins.
[dd]
> I think you should file a bug report
https://bugs.freebsd.org/bugzilla/show_bu
(Bottom-posted)
On 25/09/2014 3:48 PM, Brian W. wrote:
> You seem to be onto something. On a single user testbox I use I see this
>
> PID USERNAMETHR PRI NICE SIZERES STATE C TIMEWCPU
> COMMAND
>
> 6100 squid 1 200 612M 84076K kqread 1
You seem to be onto something. On a single user testbox I use I see this
PID USERNAMETHR PRI NICE SIZERES STATE C TIMEWCPU
COMMAND
6100 squid 1 200 612M 84076K kqread 1 4:01 0.00% squid
I then restarted squid and saw
73400 squid 1 200
; > On Mon, 2014-02-10 at 11:15 +0400, Pavel Timofeev wrote:
>>> >> So what should I do?
>>> >> Write a PR to squid's bugzilla with link to this thread?
>>> >> Fill FreeBSD ports' PR? (it seems like maintainer of squid doesn't
>>>
Am Mon, 18 Aug 2014 16:43:38 +0200
schrieb Andrea Venturoli :
> Hello.
>
> Beware anyone updating www/squid33: latest update to this ports
> overwrote my squid.conf.
>
> This might get annoying.
>
> bye
> av.
Yeah, thanks. I have just been wondering why Sq
Hello.
Beware anyone updating www/squid33: latest update to this ports
overwrote my squid.conf.
This might get annoying.
bye
av.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscri
hat should I do?
>> >> Write a PR to squid's bugzilla with link to this thread?
>> >> Fill FreeBSD ports' PR? (it seems like maintainer of squid doesn't
>> >> look at PRs about squid).
>> >> And it seems like this problem is retaled to a
Not sure what the plans are, but I'm interested in the new version as well.
On Mon, Mar 24, 2014 at 9:02 AM, Adri Koppes wrote:
> Dear Sir,
>
>
>
> I was wondering if there are any plans to support squid 3.4.x via
> FreeBSD ports soon?
>
> Version 3.4.x adds sup
Dear Sir,
I was wondering if there are any plans to support squid 3.4.x via
FreeBSD ports soon?
Version 3.4.x adds support for TPROXY and intercept using FreeBSD or
OpenBSD, which I would really like to use.
At the moment, there is no alternative to 'transparent' or 'interce
t; Fill FreeBSD ports' PR? (it seems like maintainer of squid doesn't
> >> look at PRs about squid).
> >> And it seems like this problem is retaled to all of squid ports, not
> >> only to www/squid33.
> >>
> >
> > Good question. I don't kn
On 10/02/14 16:21, Dennis Glatting wrote:
> On Mon, 2014-02-10 at 11:15 +0400, Pavel Timofeev wrote:
>> So what should I do?
>> Write a PR to squid's bugzilla with link to this thread?
>> Fill FreeBSD ports' PR? (it seems like maintainer of squid doesn't
&g
On Mon, 2014-02-10 at 11:15 +0400, Pavel Timofeev wrote:
> So what should I do?
> Write a PR to squid's bugzilla with link to this thread?
> Fill FreeBSD ports' PR? (it seems like maintainer of squid doesn't
> look at PRs about squid).
> And it seems like this prob
So what should I do?
Write a PR to squid's bugzilla with link to this thread?
Fill FreeBSD ports' PR? (it seems like maintainer of squid doesn't
look at PRs about squid).
And it seems like this problem is retaled to all of squid ports, not
only to www/squid33.
2014-02-09 23:56 GM
Found that too but not the reason why:
>
> (lldb) run -d -z -F -f /root/squid.conf
> Process 23598 launched: './src/squid' (x86_64)
> Find(): Mmapped
> Find(): IpcIo
> Find(): DiskDaemon
> Find(): Blocking
> Find(): AIO
> Returning NULL
>
> There's
On Sun, 2014-02-09 at 19:37 +0100, Dimitry Andric wrote:
> On 07 Feb 2014, at 14:24, Pavel Timofeev wrote:
> > Sorry, it has to be in freebsd-ports@ too.
> >
> > 2014-02-07 Pavel Timofeev :
> >> Hi!
> >> There is a problem with squid under FreeBSD10.0.
&g
On 07 Feb 2014, at 14:24, Pavel Timofeev wrote:
> Sorry, it has to be in freebsd-ports@ too.
>
> 2014-02-07 Pavel Timofeev :
>> Hi!
>> There is a problem with squid under FreeBSD10.0.
>> Squid crashes immediately if storage type is set to aufs.
>> It goe
Without DEBUG I got this:
#0 0x00605f71 in Fs::Ufs::UFSSwapDir::UFSSwapDir ()
[New Thread 84006400 (LWP 100348/squid)]
(gdb) bt
#0 0x00605f71 in Fs::Ufs::UFSSwapDir::UFSSwapDir ()
#1 0x005ff7c5 in
Fs::Ufs::StoreFSufs::createSwapDir ()
#2 0x004bfdf2 in
Sorry, it has to be in freebsd-ports@ too.
2014-02-07 Pavel Timofeev :
> Hi!
> There is a problem with squid under FreeBSD10.0.
> Squid crashes immediately if storage type is set to aufs.
> It goes down during read of config file.
>
> No problem with diskd. No problem with auf
05/02/14 18:41(e)an, Kevin Oberman(e)k idatzi zuen:
> Let's see. The instructions said to notify tms...@freebsd.org. I don't see
> any indication that you did so. They also say to attach the config.log
> file. I see no attached file.
>
> While it is possible that someone other than the maintaine
On Wed, Feb 5, 2014 at 5:15 AM, Enrique Ayesta Perojo <
eaye...@portugalete.uned.es> wrote:
> Hello, i have a problem trying to install Squid 3.3 or Squid 3.2 from
> ports as a transparent proxy on a fresh installed FreeBSD 10 box.
> I have the whole system sources at /usr/src
>
Hello, i have a problem trying to install Squid 3.3 or Squid 3.2 from
ports as a transparent proxy on a fresh installed FreeBSD 10 box.
I have the whole system sources at /usr/src
In the configure phase i got this error:
---
configure: choosing user-specified net I/O API kqueue
configure
1 - 100 of 160 matches
Mail list logo
