[squid-users] [RESOLVED] RE: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
> Date: Sun, 12 Jun 2011 21:23:44 +1200 > From: squ...@treenet.co.nz > To: bodycar...@live.com > CC: squid-users@squid-cache.org; squid-...@squid-cache.org > Subject: Re: [squid-users] WORKERS: Any compile option to enable? commBind: > Cannot bind socket FD 13 to [::]: (2) No such file or directory > > On 12/06/11 20:21, Jenny Lee wrote: > > > >>>> Subject: Re: [squid-users] WORKERS: Any compile option to enable? > >>>> commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory > >>>> > >>>> On 12/06/11 16:17, Jenny Lee wrote: > >>>>> > >>>>> I can't get the workers work. They are started fine. However I get: > >>>>> > >>>>> kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > >>>>> directory > >>>>> kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > >>>>> directory > >>>>> kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or > >>>>> directory > >>>>> > >>>>> Is there a compile option to enable/disable workers that I am missing? > >>>> > >>>> I can't seem to replicate that here. More details are needed about what > >>>> FD 13 and FD 9 were being used for please. > >>> > >>> > >>> 649 kid1| comm.cc(2507) comm_open_uds: Attempt open socket for: > >>> /usr/local/squid/var/run/squid-1.ipc > >>> 649 kid1| comm.cc(2525) comm_open_uds: Opened UDS FD 13 : family=1, > >>> type=2, protocol=0 > >>> 649 kid1| comm.cc(2528) comm_open_uds: FD 13 is a new socket > >>> 649 kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > >>> directory > >>> > >>> symlinking /usr/local/squid/var/run to /squid fixed the problem. I have > >>> everything in /squid. > >> > >> Aha, then you probably need to use ./configure --prefix=/squid > >> > >> That should make the socket /squid/var/run/squid-1.ipc > > > > Trimmed for brevity: > > > > strings /squid/squid|grep '^\/' > > /lib64/ld-linux-x86-64.so.2 > > /etc/resolv.conf > > /squid/errors/templates > > /dev/tty > > /dev/null > > /squid/squid.conf > > /usr/local/squid/var/run/coordinator.ipc > > /usr/local/squid/var/run/squid > > Strange those last two are UNIX sockets with address: > $(prefix)"/var/run/coordinator.ipc" > $(prefix)"/var/run/squid" > > and yet the errors and squid.conf picked up the prefix right. > > Notice how that last one has the same name as the squid binary? Yet is a > unix socket name. Strange things can be expected when you execute a > socket or try to write a data stream over a binary. Oh jesus! Apparently --prefix was added to the end of --target because of end-of-line space! strings squid|grep bindir: '--target=x86_64-redhat-linux-gnu--prefix=/squid' '--bindir=/squid' '--sbindir=/squid' ./configure \ --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu\ --prefix=/$SQUID --bindir=/$SQUID --sbindir=/$SQUID --libexecdir=/$SQUID --datadir=/$SQUID --sysconfdir=/$SQUID \ Thanks Amos! Jenny > > I suggest you let the installer use the standard FS hierarchy locations > for these special things. You can use --prefix to setup a chroot folder > (/squid) where a duplicate of the required layout will be created inside. > > > Meanwhile I'm not sure exactly how the /usr/local/squid/var/run/ got > into the binary. Maybe junk from a previous build. > Try erasing src/ipc/Makefile src/ipc/Makefile.in and src/ip/Port.o > then running ./configure and make again. > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE9 or 3.1.12 > Beta testers wanted for 3.2.0.8 and 3.1.12.2 >
RE: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
> Date: Sun, 12 Jun 2011 21:23:44 +1200 > From: squ...@treenet.co.nz > To: bodycar...@live.com > CC: squid-users@squid-cache.org; squid-...@squid-cache.org > Subject: Re: [squid-users] WORKERS: Any compile option to enable? commBind: > Cannot bind socket FD 13 to [::]: (2) No such file or directory > > On 12/06/11 20:21, Jenny Lee wrote: > > > >>>> Subject: Re: [squid-users] WORKERS: Any compile option to enable? > >>>> commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory > >>>> > >>>> On 12/06/11 16:17, Jenny Lee wrote: > >>>>> > >>>>> I can't get the workers work. They are started fine. However I get: > >>>>> > >>>>> kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > >>>>> directory > >>>>> kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > >>>>> directory > >>>>> kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or > >>>>> directory > >>>>> > >>>>> Is there a compile option to enable/disable workers that I am missing? > >>>> > >>>> I can't seem to replicate that here. More details are needed about what > >>>> FD 13 and FD 9 were being used for please. > >>> > >>> > >>> 649 kid1| comm.cc(2507) comm_open_uds: Attempt open socket for: > >>> /usr/local/squid/var/run/squid-1.ipc > >>> 649 kid1| comm.cc(2525) comm_open_uds: Opened UDS FD 13 : family=1, > >>> type=2, protocol=0 > >>> 649 kid1| comm.cc(2528) comm_open_uds: FD 13 is a new socket > >>> 649 kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > >>> directory > >>> > >>> symlinking /usr/local/squid/var/run to /squid fixed the problem. I have > >>> everything in /squid. > >> > >> Aha, then you probably need to use ./configure --prefix=/squid > >> > >> That should make the socket /squid/var/run/squid-1.ipc > > > > Trimmed for brevity: > > > > strings /squid/squid|grep '^\/' > > /lib64/ld-linux-x86-64.so.2 > > /etc/resolv.conf > > /squid/errors/templates > > /dev/tty > > /dev/null > > /squid/squid.conf > > /usr/local/squid/var/run/coordinator.ipc > > /usr/local/squid/var/run/squid > > Strange those last two are UNIX sockets with address: > $(prefix)"/var/run/coordinator.ipc" > $(prefix)"/var/run/squid" > > and yet the errors and squid.conf picked up the prefix right. > > Notice how that last one has the same name as the squid binary? Yet is a > unix socket name. Strange things can be expected when you execute a > socket or try to write a data stream over a binary. I think that is not a socket. But that is a directory where socket will reside. Most daemons now are moving to their own directories under /var/run due to selinux. squid-1.ipc and squid-2.ipc is created inside that direcotory with workers. How to find out what exactly it is from the binary? It indeed sounds alarming. But then again, I didn't face a bug in this setup that was not reproducible with stock install over the years. But now... if i indeed symlink /usr/local/squid/var/run to /squid... that last entry will point straight to squid binary. >> I suggest you let the installer use the standard FS hierarchy locations > for these special things. You can use --prefix to setup a chroot folder > (/squid) where a duplicate of the required layout will be created inside. I can't do chroot because squid interfaces with other stuff or some other stuff interfaces with squid. I am having /squid setup 9 years now. > Meanwhile I'm not sure exactly how the /usr/local/squid/var/run/ got > into the binary. Maybe junk from a previous build. > Try erasing src/ipc/Makefile src/ipc/Makefile.in and src/ip/Port.o > then running ./configure and make again. I run configure from a script and it erases squid tree and unpacks the tarball at each compile (so that I would not face issues like this). Thanks! Jenny
Re: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
On 12/06/11 20:21, Jenny Lee wrote: Subject: Re: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory On 12/06/11 16:17, Jenny Lee wrote: I can't get the workers work. They are started fine. However I get: kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or directory Is there a compile option to enable/disable workers that I am missing? I can't seem to replicate that here. More details are needed about what FD 13 and FD 9 were being used for please. 649 kid1| comm.cc(2507) comm_open_uds: Attempt open socket for: /usr/local/squid/var/run/squid-1.ipc 649 kid1| comm.cc(2525) comm_open_uds: Opened UDS FD 13 : family=1, type=2, protocol=0 649 kid1| comm.cc(2528) comm_open_uds: FD 13 is a new socket 649 kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory symlinking /usr/local/squid/var/run to /squid fixed the problem. I have everything in /squid. Aha, then you probably need to use ./configure --prefix=/squid That should make the socket /squid/var/run/squid-1.ipc Trimmed for brevity: strings /squid/squid|grep '^\/' /lib64/ld-linux-x86-64.so.2 /etc/resolv.conf /squid/errors/templates /dev/tty /dev/null /squid/squid.conf /usr/local/squid/var/run/coordinator.ipc /usr/local/squid/var/run/squid Strange those last two are UNIX sockets with address: $(prefix)"/var/run/coordinator.ipc" $(prefix)"/var/run/squid" and yet the errors and squid.conf picked up the prefix right. Notice how that last one has the same name as the squid binary? Yet is a unix socket name. Strange things can be expected when you execute a socket or try to write a data stream over a binary. I suggest you let the installer use the standard FS hierarchy locations for these special things. You can use --prefix to setup a chroot folder (/squid) where a duplicate of the required layout will be created inside. Meanwhile I'm not sure exactly how the /usr/local/squid/var/run/ got into the binary. Maybe junk from a previous build. Try erasing src/ipc/Makefile src/ipc/Makefile.in and src/ip/Port.o then running ./configure and make again. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.12 Beta testers wanted for 3.2.0.8 and 3.1.12.2
RE: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
> >> Subject: Re: [squid-users] WORKERS: Any compile option to enable? > >> commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory > >> > >> On 12/06/11 16:17, Jenny Lee wrote: > >>> > >>> I can't get the workers work. They are started fine. However I get: > >>> > >>> kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > >>> directory > >>> kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > >>> directory > >>> kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or > >>> directory > >>> > >>> Is there a compile option to enable/disable workers that I am missing? > >> > >> I can't seem to replicate that here. More details are needed about what > >> FD 13 and FD 9 were being used for please. > > > > > > 649 kid1| comm.cc(2507) comm_open_uds: Attempt open socket for: > > /usr/local/squid/var/run/squid-1.ipc > > 649 kid1| comm.cc(2525) comm_open_uds: Opened UDS FD 13 : family=1, type=2, > > protocol=0 > > 649 kid1| comm.cc(2528) comm_open_uds: FD 13 is a new socket > > 649 kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > > directory > > > > symlinking /usr/local/squid/var/run to /squid fixed the problem. I have > > everything in /squid. > > Aha, then you probably need to use ./configure --prefix=/squid > > That should make the socket /squid/var/run/squid-1.ipc Trimmed for brevity: strings /squid/squid|grep '^\/' /lib64/ld-linux-x86-64.so.2 /etc/resolv.conf /squid/errors/templates /dev/tty /dev/null /squid/squid.conf /usr/local/squid/var/run/coordinator.ipc /usr/local/squid/var/run/squid Jenny
RE: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
> >> On 12/06/11 16:17, Jenny Lee wrote: > >>> > >>> I can't get the workers work. They are started fine. However I get: > >>> > >>> kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > >>> directory > >>> kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > >>> directory > >>> kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or > >>> directory > >>> > >>> Is there a compile option to enable/disable workers that I am missing? > >> > >> I can't seem to replicate that here. More details are needed about what > >> FD 13 and FD 9 were being used for please. > > > > > > 649 kid1| comm.cc(2507) comm_open_uds: Attempt open socket for: > > /usr/local/squid/var/run/squid-1.ipc > > 649 kid1| comm.cc(2525) comm_open_uds: Opened UDS FD 13 : family=1, type=2, > > protocol=0 > > 649 kid1| comm.cc(2528) comm_open_uds: FD 13 is a new socket > > 649 kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > > directory > > > > symlinking /usr/local/squid/var/run to /squid fixed the problem. I have > > everything in /squid. > > Aha, then you probably need to use ./configure --prefix=/squid Squid is compiled with: --prefix=/squid --bindir=/squid --sbindir=/squid --libexecdir=/squid --datadir=/squid --sysconfdir=/squid --libdir=/squid --localstatedir=/squid What do i need change to get /usr/local/squid/var/run/*ipc to /squid? Jenny
Re: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
On 12/06/11 19:11, Jenny Lee wrote: Date: Sun, 12 Jun 2011 17:41:18 +1200 From: squ...@treenet.co.nz To: squid-users@squid-cache.org CC: squid-...@squid-cache.org Subject: Re: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory On 12/06/11 16:17, Jenny Lee wrote: I can't get the workers work. They are started fine. However I get: kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or directory Is there a compile option to enable/disable workers that I am missing? I can't seem to replicate that here. More details are needed about what FD 13 and FD 9 were being used for please. 649 kid1| comm.cc(2507) comm_open_uds: Attempt open socket for: /usr/local/squid/var/run/squid-1.ipc 649 kid1| comm.cc(2525) comm_open_uds: Opened UDS FD 13 : family=1, type=2, protocol=0 649 kid1| comm.cc(2528) comm_open_uds: FD 13 is a new socket 649 kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory symlinking /usr/local/squid/var/run to /squid fixed the problem. I have everything in /squid. Aha, then you probably need to use ./configure --prefix=/squid That should make the socket /squid/var/run/squid-1.ipc Shutdown issue also fixed with this. Great. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.12 Beta testers wanted for 3.2.0.8 and 3.1.12.2
RE: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
> Date: Sun, 12 Jun 2011 17:41:18 +1200 > From: squ...@treenet.co.nz > To: squid-users@squid-cache.org > CC: squid-...@squid-cache.org > Subject: Re: [squid-users] WORKERS: Any compile option to enable? commBind: > Cannot bind socket FD 13 to [::]: (2) No such file or directory > > On 12/06/11 16:17, Jenny Lee wrote: > > > > I can't get the workers work. They are started fine. However I get: > > > > kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > > directory > > kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or > > directory > > kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or > > directory > > > > Is there a compile option to enable/disable workers that I am missing? > > I can't seem to replicate that here. More details are needed about what > FD 13 and FD 9 were being used for please. 649 kid1| comm.cc(2507) comm_open_uds: Attempt open socket for: /usr/local/squid/var/run/squid-1.ipc 649 kid1| comm.cc(2525) comm_open_uds: Opened UDS FD 13 : family=1, type=2, protocol=0 649 kid1| comm.cc(2528) comm_open_uds: FD 13 is a new socket 649 kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory symlinking /usr/local/squid/var/run to /squid fixed the problem. I have everything in /squid. Shutdown issue also fixed with this. Jenny
Re: FW: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
Again. cc'ing squid-dev where the people actually working on these features can see the report. On 12/06/11 16:30, Jenny Lee wrote: I also cannot shut down squid when workers are enabled. squid -k shutdown gives "No Running Copy" I have to run a "killall -9 squid" One side effect of: --disable-kill-parent-hack Though it may be due to other things. There was a patch proposed some weeks back. Also what happens when I have 2 cores but start 7 workers? They share cores as separate instances do. Potentially getting in each others way grabbing CPU cycles. This may or may not be a problem. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.12 Beta testers wanted for 3.2.0.8 and 3.1.12.2
Re: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
On 12/06/11 16:17, Jenny Lee wrote:
I can't get the workers work. They are started fine. However I get:
kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or directory
Is there a compile option to enable/disable workers that I am missing?
I can't seem to replicate that here. More details are needed about what
FD 13 and FD 9 were being used for please.
The ports below work fine on mono squid.
---
workers 2
if ${process_number} = 1
http_port 1.1.1.1:3128
else
http_port 1.1.1.1:3129
endif
---
Thanks
Jenny
RHEL6 x64
Squid 3.2.0.7
3.2.0.8 is the current most stable beta.
Also, cc'ing squid-dev where the other dev can see this..
Compile:
--disable-carp \
--disable-wccp \
--disable-wccpv2 \
--disable-snmp \
--disable-htcp \
--disable-ident-lookups \
--disable-unlinkd \
--disable-translation \
--disable-auto-locale \
--disable-loadable-modules \
--disable-esi \
--disable-disk-io \
--disable-eui \
--disable-storeio \
--disable-auth-ntlm \
--disable-auth-negotiate \
--disable-auth-digest \
--disable-cache-digests \
--disable-ntlm-auth-helpers \
--disable-negotiate-auth-helpers \
--disable-digest-auth-helpers \
These options are now gone from 3.2:
http://www.squid-cache.org/Versions/v3/3.2/RELEASENOTES.html#ss4.3
--disable-ipfw-transparent \
--disable-ipf-transparent \
--disable-pf-transparent \
--disable-linux-tproxy \
--disable-linux-netfilter \
--without-netfilter-conntrack \
--disable-url-rewrite-helpers \
--disable-win32-service \
--disable-zph-qos \
--disable-icap-client \
--disable-ecap \
--disable-useragent-log \
--disable-referer-log \
... so are these log ones.
--disable-eui \
--disable-poll \
--disable-select \
--disable-kqueue \
--disable-icmp \
--disable-gnuregex \
--disable-cpu-profiling \
--disable-kill-parent-hack \
--disable-follow-x-forwarded-for \
--disable-forw-via-db \
--without-valgrind-debug \
--without-ipv6-split-stack \
*-ipv6-split-stack was removed in 3.1.6.
--without-po2html
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.12
Beta testers wanted for 3.2.0.8 and 3.1.12.2
FW: [squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
I also cannot shut down squid when workers are enabled.
squid -k shutdown gives "No Running Copy"
I have to run a "killall -9 squid"
Also what happens when I have 2 cores but start 7 workers?
Jenny
> From: bodycar...@live.com
> To: squid-users@squid-cache.org
> Date: Sun, 12 Jun 2011 04:17:41 +0000
> Subject: [squid-users] WORKERS: Any compile option to enable? commBind:
> Cannot bind socket FD 13 to [::]: (2) No such file or directory
>
>
> I can't get the workers work. They are started fine. However I get:
>
> kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or
> directory
> kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or
> directory
> kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or directory
>
> Is there a compile option to enable/disable workers that I am missing?
>
> The ports below work fine on mono squid.
>
> ---
> workers 2
>
> if ${process_number} = 1
> http_port 1.1.1.1:3128
> else
> http_port 1.1.1.1:3129
> endif
> ---
>
> Thanks
>
> Jenny
>
>
> RHEL6 x64
> Squid 3.2.0.7
>
>
> Compile:
> --disable-carp \
> --disable-wccp \
> --disable-wccpv2 \
> --disable-snmp \
> --disable-htcp \
> --disable-ident-lookups \
> --disable-unlinkd \
> --disable-translation \
> --disable-auto-locale \
> --disable-loadable-modules \
> --disable-esi \
> --disable-disk-io \
> --disable-eui \
> --disable-storeio \
> --disable-auth-ntlm \
> --disable-auth-negotiate \
> --disable-auth-digest \
> --disable-cache-digests \
> --disable-ntlm-auth-helpers \
> --disable-negotiate-auth-helpers \
> --disable-digest-auth-helpers \
> --disable-ipfw-transparent \
> --disable-ipf-transparent \
> --disable-pf-transparent \
> --disable-linux-tproxy \
> --disable-linux-netfilter \
> --without-netfilter-conntrack \
> --disable-url-rewrite-helpers \
> --disable-win32-service \
> --disable-zph-qos \
> --disable-icap-client \
> --disable-ecap \
> --disable-useragent-log \
> --disable-referer-log \
> --disable-eui \
> --disable-poll \
> --disable-select \
> --disable-kqueue \
> --disable-icmp \
> --disable-gnuregex \
> --disable-cpu-profiling \
> --disable-kill-parent-hack \
> --disable-follow-x-forwarded-for \
> --disable-forw-via-db \
> --without-valgrind-debug \
> --without-ipv6-split-stack \
> --without-po2html
[squid-users] WORKERS: Any compile option to enable? commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
I can't get the workers work. They are started fine. However I get:
kid1| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
kid2| commBind: Cannot bind socket FD 13 to [::]: (2) No such file or directory
kid3| commBind: Cannot bind socket FD 9 to [::]: (2) No such file or directory
Is there a compile option to enable/disable workers that I am missing?
The ports below work fine on mono squid.
---
workers 2
if ${process_number} = 1
http_port 1.1.1.1:3128
else
http_port 1.1.1.1:3129
endif
---
Thanks
Jenny
RHEL6 x64
Squid 3.2.0.7
Compile:
--disable-carp \
--disable-wccp \
--disable-wccpv2 \
--disable-snmp \
--disable-htcp \
--disable-ident-lookups \
--disable-unlinkd \
--disable-translation \
--disable-auto-locale \
--disable-loadable-modules \
--disable-esi \
--disable-disk-io \
--disable-eui \
--disable-storeio \
--disable-auth-ntlm \
--disable-auth-negotiate \
--disable-auth-digest \
--disable-cache-digests \
--disable-ntlm-auth-helpers \
--disable-negotiate-auth-helpers \
--disable-digest-auth-helpers \
--disable-ipfw-transparent \
--disable-ipf-transparent \
--disable-pf-transparent \
--disable-linux-tproxy \
--disable-linux-netfilter \
--without-netfilter-conntrack \
--disable-url-rewrite-helpers \
--disable-win32-service \
--disable-zph-qos \
--disable-icap-client \
--disable-ecap \
--disable-useragent-log \
--disable-referer-log \
--disable-eui \
--disable-poll \
--disable-select \
--disable-kqueue \
--disable-icmp \
--disable-gnuregex \
--disable-cpu-profiling \
--disable-kill-parent-hack \
--disable-follow-x-forwarded-for \
--disable-forw-via-db \
--without-valgrind-debug \
--without-ipv6-split-stack \
--without-po2html
