Update will usually work, but github's raw cdn can start caching - usually not an issue unless firing rapid requests (the install command and update point to the same URL to pull down the script)
What is your thinking on hard coded command line arguments?
On the one hand, the most flexible approach is to only specify the config file and leave the rest to the config file. On the other hand, hard coding on the command line avoids unnecessary problems from user error.
Code:
-c /jffs/configs/ntp.conf
Mandatory
-f /opt/var/spool/ntp/ntp.drift
/opt/var/spool/ntp/ntp.drift: No such file or directory
Not sure if the daemon will eventually create?
-s /opt/var/spool/ntp
Stats dir defined but no stats files
-k /opt/etc/ntp
Symmetric keys unlikely to be used
-l /opt/var/spool/ntp/ntp.log"
OK if you insist
But all update does is drag the script down I assume? Not actually run it to make any potential changes to the environment (like creating a dir). Just thinking if any other changes are made in the future relating to where stuff is stored then you’d have to manually run install after update again.
But all update does is drag the script down I assume? Not actually run it to make any potential changes to the environment (like creating a dir). Just thinking if any other changes are made in the future relating to where stuff is stored then you’d have to manually run install after update again.
After I removed the previous manual installation, your script worked without a hitch. Very impressed at how quickly you pulled this together. Just waiting for some data to show in the graphs... Thank You Jack!
Sorry, there may be a command line option "-g" that we need. If the time offset is large at startup, ntpd may exit. This would be the case on router reboot.
-g
Normally, ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default. This option allows the time to be set to any value without restriction; however, this can happen only once. If the threshold is exceeded after that, ntpd will exit with a message to the system log. This option can be used with the -q and -x options. See the tinker command for other options.
Sorry, there may be a command line option "-g" that we need. If the time offset is large at startup. ntpd may exit. This would be the case on router reboot.
-g
Normally, ntpd exits with a message to the system log if the offset exceeds the panic threshold, which is 1000 s by default. This option allows the time to be set to any value without restriction; however, this can happen only once. If the threshold is exceeded after that, ntpd will exit with a message to the system log. This option can be used with the -q and -x options. See the tinker command for other options.