> >> Subject: Re: 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
