Chrooted Bind printing wrong time and compile path in log

[Colin Stefani]

I just compiled BIND 8.2.2 p7 and installed it. A funny thing is getting
reported to the logs...

Background: we are using a Sun Netra w/Solaris 7, named runs in a chrooted
jail that has worked wonderfully since it's installation. 'named' runs as
user 'named' and under group 'named'. Permissions in the jail or fine and
secure.

I compiled the new binary of 8.2.2 p7 in another directory on a different
system (a "source code" directory on another identical machine) using gcc.
The compile went fine, the only change made was the install paths in the
src/port/solaris/Makefile.set to reflect how our jail is set up (we don't
use /usr/local/bind, the paths in the jail are a little different).

I installed the binaries and relevant lib's in the chroot'd jail and fired
up named to see what would happen. In the log, named reported to the
'daemon' facility this entry (yes, that's a bogus hostname)  :

    Nov 17 00:05:10 host.domain.com named[10719]: starting.  named 8.2.2-P7
Thu Nov 16 15:21:18 PST 2000
    Nov 16 16:05:10 host.domain.com
root at host.domain.com:/usr/local/source/bind/src/bin/named

Two things are happening, the time of the initial named launch is wrong (it
looks like GMT) and the second line shows the compile directory where BIND
was compiled originally. It's kinda freaky and I've never seen it do this
before. Any ideas? It's not a critical issue, as the rest of BIND seems to
function properly, I'm just worried I overlooked something or make an error
somewhere. The time difference thing I think is the named daemon starting up
and then correcting it's launch time as it gets chrooted. The jail has the
proper time files and system libs for this, as the previous named didn't
have any of this behavior.

I am using Sun's chrooted binary to launch the named process with this
command:

    host% /usr/sbin/chroot /chroot/named /usr/bin/named -u named -g named

If launched NOT chrooted the time problem goes away, but the path printing
doesn't. Also, the previous version (8.2.2 p5) didn't do this, the
named.conf file hasn't changed either. 

Any ideas?

Thanks for your help,

Colin

---------------------------------------------------------------
"The path of least resistance is what makes the river crooked"
                                                  -Utah Philips