squid requires FQDN and does not report an error

[martyscholes]

Binary package hint: squid

This *might* be considered a dupe of rejected bug 12709, which the Debian guys decided was a non-issue.

In Ubuntu, I find it most convenient to have squid (or some other caching proxy server installed), especially for a box which has multiple users.

The bug here is that it does not "just work."

To reproduce, start Synaptic, install Squid and then (incorrectly) assume it is working, since no errors will be reported to the casual user, even though it has refused to start. Most home/laptop/non-server installations will not have a FQDN available.

Squid simply will not run, throwing an error which cannot be detected unless user is sophisticated enough to check the logs or run:

sudo /etc/init.d/squid start

and watch for errors.

From a perspective of making Ubuntu "just work," this seems unreasonable. I understand that the only reason squid cares about a FQDN or visible_hostname is so that it knows what to put into the logs. Cannot squid be modified to assume SOMETHING when it lacks a visible_hostname or FQDN, like "hostname -f"?

Marty

[Chuck Short (zulcss)]

You should be able to set visible_hostname in the configuration file.

chuck

[martyscholes (martyscholes)]

Chuck,

I don't blame you for changing the status.

If memory serves, squid now "just works" with the
default config.

Marty

--- Chuck Short <email address hidden> wrote:

> You should be able to set visible_hostname in the
> configuration file.
>
> chuck
>
> ** Changed in: squid (Ubuntu)
> Status: New => Won't Fix
>
> --
> squid requires FQDN and does not report an error
> https://bugs.launchpad.net/bugs/97505
> You received this bug notification because you are a
> direct subscriber
> of the bug.
>

      ____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com