the_ntp_functions
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| the_ntp_functions [2017/03/18 11:38] – [Synchronising Clients] walkeradmin | the_ntp_functions [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 190: | Line 190: | ||
| \\ | \\ | ||
| {{: | {{: | ||
| + | \\ | ||
| \\ | \\ | ||
| Select ' | Select ' | ||
| Line 252: | Line 253: | ||
| \\ | \\ | ||
| - | + | ---- | |
| - | + | ==== Clients over 1000 Seconds out of time ==== | |
| - | + | \\ | |
| - | + | “NTP won’t normally reset the clock if it’s off by more than 1000s. If you run: | |
| - | + | < | |
| - | + | ntpd -gq’ | |
| - | + | </ | |
| + | It ignores the clock being way adrift from ntp time and will force it to be correct then close. The old ntpdate program does the same thing.” | ||
| + | \\ | ||
| + | \\ | ||
| + | Credit: [[http:// | ||
| + | \\ | ||
| + | \\ | ||
| ---- | ---- | ||
| + | ==== Raspberry Pi Dropping of Wireless Network ==== | ||
| - | ==== to do ==== | + | I found my raspberry Pi Zero, that is using the official Raspberry Pi Wireless Dongle drops off the wireless network after around a week. Only a reboot gets it back (as I have no keyb/mouse connected) so I figured just using Cron to reboot the thing every 24 hours will be a suitable work around. |
| + | \\ | ||
| + | \\ | ||
| + | To use cron (should already be installed): | ||
| + | \\ | ||
| + | \\ | ||
| + | sudo crontab -e (reboots require super user rights) | ||
| + | \\ | ||
| + | Insert the following line: | ||
| + | \\ | ||
| + | \\ | ||
| + | 0 0 | ||
| + | \\ | ||
| + | Explanation: | ||
| + | \\ | ||
| + | \\ | ||
| + | < | ||
| + | m h dom mon | ||
| + | minute hour dayOfMonth Month dayOfWeek commandToRun | ||
| - | wireless dropping out on ntp server | + | so the line |
| + | 0 0 | ||
| + | would reboot your system every day at 00:00. | ||
| + | </ | ||
| + | \\ | ||
| + | Use Ctrl+X, Y, Enter. This will save and exit crontab (if using nano) | ||
| + | \\ | ||
| + | \\ | ||
| - | clients over 1000seconds out | ||
| - | |||
| - | “NTP won’t normally reset the clock if it’s off by more than 1000s. | ||
| - | If you run ‘ntpd -gq’ it ignores the clock being way adrift from ntp time and will force it to be correct then close. The old ntpdate program does the same thing.” | ||
| - | credit: I found it here earlier today when I was searching on some raspi NTP issues | ||
| - | http:// | ||
| - | Reply | ||
the_ntp_functions.1489837121.txt.gz · Last modified: 2023/03/09 22:35 (external edit)