Tiny Core Base > TCB Bugs
getTime.sh not working at startup
Stefann:
Hi,
I hope I do this right but anyway...
When I startup tiny core the time is not synced.
running getTime.sh as user also does not sync it
running with sudo does
What I did:
--- Code: ---Give clock a 3minute error, than REBOOT....
tc@hp510:~$ sudo reboot
==================
after reboot:
tc@hp510:~$ date
Fri May 2 13:20:09 CEST 2025. //this is wrong
tc@hp510:~$ getTime.sh
tc@hp510:~$ date
Fri May 2 13:20:21 CEST 2025. //still wrong
tc@hp510:~$ sudo getTime.sh
tc@hp510:~$ date
Fri May 2 11:18:06 CEST 2025. //OK now
tc@hp510:~$
--- End code ---
For reference, my extlinux.conf:
--- Code: ---DEFAULT gui16
LABEL gui16
KERNEL /tce/boot/vmlinuz16
INITRD /tce/boot/core16.gz
APPEND quiet host=hp510 tz=CET-1CEST,M3.5.0,M10.5.0/3 waitusb=5:UUID="ab0b387d-7533-4e69-a8ac-ee5ab733c5f7" tce=UUID="ab0b387d-7533-4e69-a8ac-ee5ab733c5f7"
--- End code ---
tested on TC16
also tested on TC15 >> same behaviour
In itself this is not a big deal, I can easily add sudo getTime.sh to boot local.sh
Just want to understand whether I do something wrong
Paul_123:
It runs automatically if you are using dhcp for your network. But it will timeout after 60s if the network does not have an address.
If you use a static network configuration, the you need to manage it all manually.
Stefann:
As far as I understand (I'm not a guru) I'm using dhcp:
- I'm assigning it a fixed address from my router but I consider that dhcp (right?)
- I have no config files in .filetool.lst, only network related is "usr/local/etc/httpd/httpd.conf" but that is apache only I think.
- also not other files in /opt or /opt (but I may overlook something)
And I'm booting below 60seconds:
- I'm booting in 39seconds towards a ssh prompt
So I feel "it should have worked" out of the box.
Note: running 32bit version on 64bit Via Eden cpu
Any "tip" on how to debug this further?
> like "where is it called" such that I can potentially check a bit what happens.
mmmh... maybe I should modify the getTime.sh such that it creates a logging
Paul_123:
It’s not the boot time, it’s how long it takes for you to get a network address. ntp is also not instantaneous when syncing a time.
It’s called from /etc/init.d/tc-config. (Near the end). /etc/inti.d/settime.sh is what gets called.
Stefann:
thanks,
I'll check what happens.
ehh... if I got an ssh connection from a remote computer 39seconds after start, the network connection should also have been there within that 39seconds.
Anyway... no worry... I'll figure that out.
thanks for pointing me into a direction
(expect it to take a day or so before I have an update)
Navigation
[0] Message Index
[#] Next page
Go to full version