This might be the the SUSE-shipped squid
> SUSE Squid rcsquid start --> i think without the -f parameter
> compiled squid --> /usr/local/sbin/squid -N
The rcsquid is only a start-script and normal start the /usr/local/sbin/squid . Thus both is SUSE-shipped.
Just type "squid -v" to see the correct version.
Your cooperation is welcome.
Mit freundlichen Gr��en, Volker Neise
S�d-Chemie AG, Munich
Corporate Information Management - Internet / Intranet
Tel. ++49-89-5110-428
Fax ++49-89-5110-71428
> -----Urspr�ngliche Nachricht-----
> Von: news [mailto:news@sea.gmane.org] Im Auftrag von Christian Klinger
> Gesendet: Montag, 6. Dezember 2004 14:36
> An: squid-users@squid-cache.org
> Betreff: [squid-users] Re: squid -k reconfigure crash
> parallel instances
>
> Venkatesh K wrote:
> > On Mon, 06 Dec 2004 13:47:22 +0100, Christian Klinger
> > <cklinger@novareto.de> wrote:
> >
> >>Hello List,
> >>
> >>first i�m not a squid expert!
> >>
> >>I think i have a stupid problem! I use one squid direct from SUSE
> >>Distrubition for our internet proxy, and one squid (self compield
> >>Version 3.0-PRE3) as reverse proxy.
> >>
> >>Now the Problem!
> >>
> >>If i run "squid -k reconfigure" from the "SUSE-Squid" i
> think i crash
> >>the compiled squid!
> >>
> >>Any tips ?
> >
> >
> > For each instance you will have a config file. You can do
> >
> > # squid -k reconfigure -f <config_file_path_for_this_instance>
> >
> > This should solve your problem.
> >
> > Venkatesh K
> >
> >
> >>thx christian
>
> Thx for your fast answer! But it has the same bad effect! Maybe it
> depends on how i start the two squid servers.
>
> SUSE Squid rcsquid start --> i think without the -f parameter
> compiled squid --> /usr/local/sbin/squid -N
>
> - christian
>
>
Received on Mon Dec 06 2004 - 07:25:04 MST
This archive was generated by hypermail pre-2.1.9 : Sat Jan 01 2005 - 12:00:01 MST