Search squid archive

Re: squid.conf.documented instead of squid.conf?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/14/2010 04:02 PM, Boniforti Flavio wrote:
> Hello list.
> 
> I'm on Debian SID and wanted to update squid3 to the latest 3.1.1-2
> version. What happened is that dpkg returned me following error:
> 
> Configurazione di squid3 (3.1.1-2)...
> sed: errore di lettura su stdin: Is a directory
> dpkg: errore nell'elaborare squid3 (--configure):
>  il sottoprocesso vecchio script di post-installation ha restituito lo
> stato di errore 4
> Si sono verificati degli errori nell'elaborazione:
>  squid3
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> The *second* line is the one that made me investigate a little bit:
> "sed: error reading stdin: Is a directory"... Thus I checked /etc/squid3
> and got this:
> 
> drwxr-xr-x  2 root root 4096 14 apr 15:54 squid.conf
> 
> Entering that directory, I discovered:
> 
> -rw-r--r-- 1 root root 198563 12 apr 16:09 squid.conf.documented
> 
> My questions are:
> 
> A) where did my customized squid.conf disappear to?
> B) is it normal that now the /etc/squid3/squid.conf is not anymore a
> file, but a directory?
> C) how can I extract the actual configuration from the running squid3?

I would say, instead of asking here in the squid mailing list, you
should better file a bug report against the debian package. Looks like
something is wrong there. I don't think this is a Squid problem.

-- Matthias

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux