RE: [squid-users] Patch Installation Procedure and Weirdness Afte rwards

Indeed I am using aufs, and thank you for the explanation. For grins, here
is the 'confused' pstree:

init-+-aacraid
     |-cron
     |-httpd---6*[httpd]
     |-inetd
     |-keventd
     |-khubd
     |-2*[kjournald]
     |-klogd
     |-kreiserfsd
     |-mdrecoveryd
     |-6*[mingetty]
     |-nscd---nscd---5*[nscd]
     |-ntpd
     |-portmap
     |-squid-+-squid---32*[squid]
     | |-32*[squid_redirect]
     | `-unlinkd
     |-sshd---sshd---sshd---bash---pstree
     `-syslogd

Grant

-----Original Message-----
From: Henrik Nordstrom [mailto:hno@squid-cache.org]
Sent: Tuesday, January 14, 2003 2:55 PM
To: Sturgis, Grant
Cc: 'squid-users@squid-cache.org'
Subject: Re: [squid-users] Patch Installation Procedure and Weirdness
Afterwards

Are you using the "aufs" cache_dir type on Linux? Then it is only the
Linux ps tool who is getting confused, not multiple instances of Squid..

In fact, Squid won't start multiple instances unless you carefully
cenerate specific squid.conf files for each. Once a squid is running the
http_port etc specified is blocked by that Squid and no new squid can be
started with the same configuration (if you manage to convince Squid to
start it will quickly abort in such case as it cannot follow your
configuration).

Regards
Henrik

"Sturgis, Grant" wrote:
>
> Thank you Henrik for the reply.
>
> I was able to edit RunCache and get the binary in sbin to start up, but I
am
> still having a problem with multiple instances of squid starting. I have
> allowed the startup script to call RunCache, which in turn starts
> $PREFIX/sbin/squid, but then many other instances fire up as well. I
> currently have 34 squids running. I have also disabled the startup script
> and started it manually (with /usr/local/squid/sbin/squid -NsY) but the
same
> thing happened.
>
> I do not see any problems in cache.log or any obvious reason as to why
this
> is happening, but I am sure I am missing something.
>
> Any suggestions for what is going on and how I can fix it?
>
> Thanks,
> Grant
>
> -----Original Message-----
> From: Henrik Nordstrom [mailto:hno@squid-cache.org]
> Sent: Friday, January 03, 2003 5:04 PM
> To: Sturgis, Grant
> Cc: 'squid-users@squid-cache.org'
> Subject: Re: [squid-users] Patch Installation Procedure and Weirdness
> Afterwards
>
> "Sturgis, Grant" wrote:
> >
> > Thanks Robert for the response.
> >
> > After ./configure and make, I checked the new binary in the src
directory,
> > it had the correct configure options (--enable-snmp and
> > --enable-storeio=ufs,aufs,diskd) and I made a note of it's md5sum.
After
> I
> > ran the make install, the new binary was installed in
> /usr/local/squid/sbin
> > but the old binary remained in /usr/local/squid/bin. I was concerned
> since
> > RunCache executes the binary in PREFIX/bin, so I copied the one in
> > PREFIX/sbin to ../bin. Is this a mistake?
>
> Change your RunCache script to run Squid in sbin, or start Squid
> directly.
>
> Squid will stay in sbin for future versions. Any references to Squid
> beeing in bin should be exterminated.
>
> Regards
> Henrik
> This electronic message transmission is a PRIVATE communication which
> contains information which may be confidential or privileged. The
> information is intended to be for the use of the individual or entity
named
> above. If you are not the intended recipient, please be aware that any
> disclosure, copying, distribution or use of the contents of this
information
> is prohibited. Please notify the sender of the delivery error by replying
to
> this message, or notify us by telephone (877-633-2436, ext. 0), and then
> delete it from your system.
This electronic message transmission is a PRIVATE communication which
contains information which may be confidential or privileged. The
information is intended to be for the use of the individual or entity named
above. If you are not the intended recipient, please be aware that any
disclosure, copying, distribution or use of the contents of this information
is prohibited. Please notify the sender of the delivery error by replying to
this message, or notify us by telephone (877-633-2436, ext. 0), and then
delete it from your system.
Received on Tue Jan 14 2003 - 15:20:40 MST