Re: INN and docker default hostnames

On Friday, 20 September 2024 at 12:12, Julien =C9LIE wrote:
[...]
> I suggest to also recognize an INN_HOSTNAME environment variable, if set.
> Wouldn't it solve the problems when using Docker or like?
> =

> We already read some environment variables like INNCONF (alternate path to
> inn.conf), NNTPSERVER, INND_BIND_ADDRESS, INND_BIND_ADDRESS6, FROMHOST,
> ORGANIZATION, and UU_MACHINE.
> =

> Why not have the following behaviour for the hostname:
> - the INN_HOSTNAME environment variable if fully qualified;
> - the result of gethostname(3) if fully qualified;
> - the result of getaddrinfo(3) if fully qualified;
> - the concatenation of "hostname.domain" where hostname is the result of
> gethostname(3) and domain the value of the eponym parameter in inn.conf.

Perhaps INND_HOSTNAME would be better for consistency with the existing
INND_* variables?

Regards,
Dominik
-- =

Fedora   https://fedoraproject.org
Deep in the human unconscious is a pervasive need for a logical universe th=
at
makes sense. But the real universe is always one step beyond logic.
        -- from "The Sayings of Muad'Dib" by the Princess Irulan
-- =

inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers