Hi Luigi, you are right. There seems to be a temporarily problem with squid.conf. I didn't remember well, but now I'm sure that I had pulled package squid as a dependency of package squidguard, which itself was pulled from my custom-build package as (only) dependency. My package edits squid.conf during its installation. I have hardly tried to find out what happend, but I don't have any explanation.
If I choose squidguard with aptitude, squid, squid-common and libdb4.1 get also installed. Everything works fine. Then I can install my package, still fine. I can stop squid, delete the cache files and swap.state, call squid -z and rebuild the cache. When starting squid again, everything is all right. Squid does not complain about my squid.conf and the file owner is proxy.proxy. The problem does only occure when squid is pulled as dependency of my package. Some strange kind of unlucky interaction. I'd propose to close that bug report. I'm sorry for steeling your time. Saluti a Roma Hans Am Freitag, 2. Dezember 2005 02:47 schrieb Luigi Gangitano: > Hi Hans, > in the logfile you provided (which is attached again for > the record in the bug tracking software), I found these > lines at the end of the first execution of squid: > > 2005/11/27 18:13:24| storeDirWriteCleanLogs: Starting... > 2005/11/27 18:13:25| Finished. Wrote 0 entries. > 2005/11/27 18:13:25| Took 0.0 seconds ( 0.0 > entries/sec). FATAL: Bungled squid.conf line 2: > http_access deny all Squid Cache (Version 2.5.STABLE9): > Terminated abnormally. > > It seems that you first started squid with a uncorrect > squid.conf and startup terminated abnormally before > ownership of /var/spool/squid/ swap.state was set > correctly. This can happen since squid drops root > privileges late in the startup process, expecially the > first time it is executed. > > Please check the /etc/squid/squid.conf file for the error > on line 2. > > Regards, > > L > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
