*almost* everything came up, except dovecot, which complained about a really bad time jump.
at least my ipv6 still works. :)
RandalSchwartz: time jump while booted or between boots?
Not sure.
Feb 16 03:09:01 red dovecot: Fatal: Time just moved backwards by 28798 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards
just before that: Feb 16 11:08:57 red dovecot: Dovecot v1.2.17 starting up
oh wow that's a huge jump back
so it must've thought the time was wrong at first.
looks to be 6 hours
oh 8 hours :)
maillog shows stuff at 2:39, then 3:09 eventually
the middle part must be while my system was being rehosted
Yeah - 8 hours would be GMT, so maybe it took a GMT time on boot
yeh
it may be an order thing
yeah - my messages file shows 11-am-ish times
so it definitely thought it was on GMT until everything finished warming up
starting dovecot later in boot may help
... Feb 16 11:08:36 red syslogd: kernel boot file is /boot/kernel/kernel
... Feb 16 11:08:52 red ntpd[641]: ntpd 4.2.8p9-a (1): Starting
so ntpd must've fixed it.
because the timestamps are fixed after that.
I've rebootted before, without this happening...
oh i wonder if it thinks that the clock should be in local time when it's in UTC or such
I suspect this is just a consequence of being moved.
yeah - maybe it's a setting of the emulator.
or something I should have set in freebsd
sounds like a TZ thing to me
yeah, perhaps freebsd wants to maintain the hardware clock in localtime, but it initially woke up in UTC.
tzsetup should be able to adjust it
No - I already have it correct.
hmm
Thu Feb 16 11:53:25 PST 2017
tzsetup also controls local/UTC
Oh hmm.
Maybe that's set wrong for me.