Server insists on wrong hostname
Kevin Oberman
rkoberman at gmail.com
Sat Oct 11 18:51:25 UTC 2014
On Sat, Oct 11, 2014 at 9:33 AM, Christian Alge <lists at burnus.net> wrote:
> That returns nothing.
> > Well, a rather "brute force" approach would be:
> >
> > grep -r 'Freie Energie' /etc/
> >
> > (Mind, you may need root access to avoid "permission denied" messages
> > -- or you culd just ignore them, if you are confident that the files
> > in question are sufficiently unlikely to be at fault.)
> >
> > If that fails, I have a possible other approach in mind, but it's a bit
> > of a mess, so I'd rather not even try to describe it unless nothing else
> > works.
> >
> > Peace,
> > david
> >
>
I suspect some script is executing a hostname(1), but this is just
guessing. I'd suggest adding "hostname" in a few places in startup scripts
(/etc/rc.d and /usr/local/etc/rc.d). If you see which script is doing it,
use rcorder(8) to see what scripts could be triggering it. Turning on
debugging in startup may also help, but will produce a LOT of output during
startup and shutdown. (Set rc_debug="YES")
Unrelated, but important... you mentioned editing /etc/defaults/rc.conf.
This is a VERY bad idea. Those scripts are always overridden by the
matching scripts, if any, in /etc. System upgrades assume that they are
untouched and changing them can really break things. If /etc/rc.conf has a
"hostname="freieenergie" line, it will override anything in
/etc/defaults/rc.conf.
More information about the freebsd-stable
mailing list