Fixing DST manually on rel4 & rel5

[Ken Cochran]

Hello -questions:

This is most certanly a FAQ but I'm not yet finding the kind of
answer I need...

I have a couple of old FreeBSD systems that I can't (yet) update
to the new Daylight Saving Time rules (based on the email message
that came out on -announce in late February).  One is
4.10-stable, last updated late November 2004 & the other is
5.4-release.  Cvsup brings /usr/src in order but I can't update
ports (yet) to get misc/zoneinfo and it doesn't look like I can
just "transfer" the /usr/share/zoneinfo bits over from /usr/src
without a {build,install}world (also impractical at this time).

Best I can tell from the message that came from -announce sometime
back, the same fix(es) would apply to both the 4 & 5 branches.

Is there a "proper" way to fix the timezone on these machines
"manually" pending the "real" change that will happen in the
system according to the previous rules/schedule?  (e.g. Fix it
temporarily/manually but not clobber the original rules.)

Or is there some way to install the new cvsup'ed zoneinfo bits
into an "old" system so I can run tzsetup and have everything
fixed "correctly?"  I'm in US Central timezone and I've seen it
reported as CST6CDT (I guess that's in SysV).

FAQ/doc/book pointers/references are welcome of course - I'm
still digging around in both the Handbook & Complete FreeBSD
and wherever else I can find...

Many thanks,

-kc
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

4.10-stable nameserver strange behavior

[Ken Cochran]

Hi:

How I "refresh" a system binary?

More specifically, I think I may have a compromised(?) named
in /usr/sbin but what I have in /usr/obj should be fine;
if not I still have it in /usr/src and can rebuild/reinstall it.

So how would I do the "named only" part of an installworld?

Or, to take it another step back, how to do the "named only"
part of a buildworld, followed by the "named only part of an
installworld?

I have the dead-tree versions of both the Handbook & Lehey's
book.  Or, where might I find this/these procedures documented?

Actually, what has really happened is a "wierdness" I'm trying
to correct:  (Maybe my named has been compromised somehow but
there have been no messages in the nightly security runs.)

In the wee hours of the morning, my upstream cablemodem provider
dhcp'ed me a new ip-address.  Ok, fine...  (Dhclient seems
working fine from what the system log & tcpdump are showing.)

I can ping/traceroute (to) my system from outside (proper stuff
shows up in tcpdump too) but I can't ping/traceroute *from*
my system to anywhere (not even by ip-address).  I can ping
"myself" (the newly assigned ip-address just fine.

Hmm, name service isn't working correctly (I run a local
cache-only DNS, BIND 8.3.7, ya, old but someday...), so I kill &
restart named.  The appropriate named startup messages appear
in the messages-log, e.g. "listening on [new ip-address].
Here's the wierd part: tcpdump shows DNS "priming" requests
(to the various *.root-servers.net addresses) with a *source* ip
of my *previous* ip-address, not the new one.  So far, *no* NS
requests show the proper source address; they all show the old
ip-address & not the new one.  Also, so far, behavior survives
reloading, restarting & completely killing & restarting named.

Umm... what else can I think of...  No external IPs are in the
named config and/or zone files, only local 192.168 & 127 things.
I can't find any zombie processes so far(?)

OS is:
 4.10-STABLE FreeBSD 4.10-STABLE #0: Sun Nov 28 03:17:35 CST 2004

Yes, I know, very old...  I do plan to upgrade...  This system
is very creaky nowadays & I'm very reluctant to reboot it;
might not come back up.  :(

Ideas?

Many thanks,

-kc
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"