Yes I saw it was the timeserver, but I noticed after I already posted my previous post.
In my logs I was seeing Freesco trying to translate my timeserver domain via DNS.
The strange thing is... when I tested this, the Lappy did have access to the internet via my current Freesco (033) because the 1st thing I did when all was up and running, was to download your MC package
but I'll check it out.
Now that the install is still "fresh" I think I'll upgrade to 037, or is 038 being released any time soon?
Just a quick update...
I noticed that when booting and Freesco "hangs" with the synctime... Freesco isn't pingable either, nor can it ping to the outside world (From TTY2).
To be sure it's no firewall rule... I added 2 rules in the rc_user
to allow anything.
But it still didn't work...
However... when I log into the 2nd console and do an rc_main restart
, Freesco can be pinged immediately, and the synctime process finishes too...
This only works with the rc_main restart
. An rc_net restart
, for example, does not work.
Also, if I change the kernel to kernel-037.vipc-ipsec
(because I need vipc for Apache), Freesco displays the same problem.
Freesco does not "freeze" all
the time, it just occasionally does.