Your message dated Thu, 16 Nov 2006 12:13:45 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Closing bug in woody
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: squid
Version: 2.4.6-2
Severity: normal
I upgraded to Woody and now have started getting an error message from
Cron every morning. I managed to track this down to an apparently
unsupported directive in my /etc/squid.conf
From: [EMAIL PROTECTED] (Cron Daemon)
To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> test -e /usr/sbin/anacron || run-parts
--report /etc/cron.daily
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env:
<PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
Message-Id: <[EMAIL PROTECTED]>
Date: Mon, 29 Jul 2002 06:27:32 +0300
/etc/cron.daily/logrotate:
2002/07/29 06:26:13| parseConfigFile: line 97 unrecognized:
'tcp_incoming_address 127.0.0.1'
As you can see, there is no indication whatsoever that this message
comes from Squid.
I'd like to ask for a fix, but I don't know what would be appropriate.
Here's a quick list from easiest and least desirable, to (probably)
hardest and most desirable.
0. Adequately tag error messages so that logrotate message clearly
identifies Squid as the culprit when there's an error
1. Run some sort of validation on the config file when upgrading, and
prevent configuration from completing if there is an error
2. Run some sort of validation on the config file when upgrading from
an older version, and help the user to fix any problems
3. Identify and replace obsolete directives in the config file when
upgrading
FWIW, I was running whatever was "stable" before (Debian potato) and
did a dist-upgrade recently. I have a transcript from the apt dist-upgrade
but IIRC it didn't contain anything directly relevent (and it's huge).
Apparently, the fix for my particular problem is to use a variant of
the http_port directive.
See also bug #144255. Item #0 on the list above (at least) makes this
a different bug from that one, though, IMHO.
/* era */
-- System Information
Debian Release: 3.0
Kernel Version: Linux there 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown
Versions of the packages squid depends on:
ii adduser 3.47 Add and remove users and groups
ii debconf 1.0.32 Debian configuration management system
ii libc6 2.2.5-10 GNU C Library: Shared libraries and Timezone
ii libldap2 2.0.23-6 OpenLDAP libraries.
ii logrotate 3.5.9-8 Log rotation utility
ii netbase 4.07 Basic TCP/IP networking system
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm closing this bug since it applies to old versions of Debian
(potato and woody) which are not supported anymore.
Regards,
- --
Luigi Gangitano -- <[EMAIL PROTECTED]> -- <[EMAIL PROTECTED]>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
iD8DBQFFXEfr8ZumGJJMDCYRAjn5AJ49NlTveNsN805w19Pis76AzqWQ7ACcCn89
22vS8+zZTsFeqAVKQCbm0AE=
=c0LU
-----END PGP SIGNATURE-----
--- End Message ---
