On Fri, 02 Mar 2012 18:16:45 -0500, Gary Palmer <gpal...@freebsd.org> wrote:
> Does the datestamp on /usr/sbin/named reflect when you built the world
> or could named have been left over from a previous install?
>
> WITHOUT_BIND="yes" doesn't delete named if its already installed (not
> sure
> if 'make delete-old' cleans it up or not)
"stat /usr/sbin/named" leaves me in shame - yes, it is left over from
a previous buildworld. (Thanks also to others, whose suggestion of
same problem just came in from where I sit.) On to next problem...
> As for named running, if you do
>
> sh /etc/rc.d/named restart
>
> does it succeed? If so, the 'named_enable="no"' flag must be set wrong.
"sh /etc/rc.d/named restart" gives exactly what you would expect
("Cannot `restart` named. Set named_enable to YES...").
> Also check to make sure that its not named from ports or some other
> location (e.g. check fstat or lsof or something to make sure its actually
> /usr/sbin/named and not from some other location)
"fstat | grep /named" returns nothing (!), likewise "fstat | grep
/sbin". However:
# procstat -b `pgrep named`
PID COMM PATH
63121 named /usr/sbin/named
63090 named /usr/sbin/named
(I also never used ports BIND.)
I would really like to figure this out before I do the necessary work
to remove unwanted BIND from the system. Processes running without
apparent reason, indicates something else is wrong.
Thanks for the help so far. I am continuing to poke the system, just
looking for the right tool to find out how this got started (also
grepping logs which show start but don't seem to show why).
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
