Date: Fri, 03 Jul 2009 10:00:21 +1000 From: Danny Carroll <danny@dannysplace.net> To: fbsd@dannysplace.net Cc: Bill Moran <wmoran@potentialtech.com>, freebsd-questions@freebsd.org Subject: Re: Strange startup behaviour. Message-ID: <4A4D4A15.5020006@dannysplace.net> In-Reply-To: <4A4D3ADA.50601@dannysplace.net> References: <4A4CC4F1.6080303@dannysplace.net> <20090702110159.8a175688.wmoran@potentialtech.com> <4A4D3ADA.50601@dannysplace.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Danny Carroll wrote: > That would surprise me. The thing that looked strange to me was that > there was a heap of files in /etc/rc.d/ that look like they had not been > accessed since the last shutdown of the machine. I think I figured out this behaviour. I believe that the access times are different because at boot time adjkerntz runs and sets the correct time (or rather zone) during boot. The times are 10 hours apart which is the difference between UTC and my time zone. It was a strange co-incidence that I rebooted my machine yesterday twice, the second time was almost 10 hours after the first which is why I was confused. Perhaps if the clock was set to UTC then this would not happen. It still does not explain why /etc/rc.d/natd does not start natd at boot. I also tried copying /etc/rc.d/natd to /usr/local/etc/rc.d in the thought that this was a chicken/egg problem and /usr/local/etc/rc.d scripts might run late enough to work. But I still need to restart natd manually. -D
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A4D4A15.5020006>