severity 396028 normal
retitle 396028 Fails to start on machines lacking FQDN and
visible_hostname
merge 396028 299431
thanks
Hi Falk,
squid needs a 'name' for the instance. It could get it from the
hostname or from the configuration file.
Configuration file setting takes precedence on the system hostname
(this is needed to be able to override system-wide settings) and thus
is impossible to ship squid with a default visible_hostname setting.
The installation process takes information provided by the
administrator to set a proper hostname on the machine. If something
fails in this process (because of an human error or a program error),
the machine is left with no hostname and squid fails to start since
it cannot work properly.
There are two solutions for this:
- fix the hostname setting of the machine
- override missing hostname information in squid configuration file
Neither of them can be done at the package level, since this is not a
package bug.
A better search in the BTS for squid would point you to bug #294431,
which is exactly the same bug as this. I'm now downgrading severity
of this bug since it can be resolved easily with a minor
configuration change (and it doesn't make squid 'unusable'),
retitling it to something more insightful and merging it with the
previous bug.
Regards,
--
Luigi Gangitano -- <[EMAIL PROTECTED]> -- <[EMAIL PROTECTED]>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
