I moved my main setup from an AC86 to an AX88, which seems to boot much faster. I have a lot of addons, including diversion. Part of my setup is a nonstandard scribe install that depends on ntp having synced (I'll explain below). That worked fine on the AC86 but not on the AX88, because it seems to start before ntp syncs. So I inserted an ntp hold as part of my startup (the normal hold, without a lock file but with an escape loop). Then it worked fine.
I sort of vaguely assumed that entware didn't start until ntp syncs, but I see that a more than a few addons have ntp checks. I get that if ntp has synced the addon will immediately go on its merry way, but some wait 30 seconds for the next check, I think. So there could be several addons waiting during the boot process before they actually start.
So I'm wondering if there should be a straight off single check/wiat for all the addons, and where in the hooks it should be. Or, maybe there is?
TL;DR
The standard scribe install appends the starting log to the messages file. I like to see the messages file as a single file with the current boot and a proper timestamp. I never feel the need to go back to older messages files, but I do want to see what might have been logged before the router rebooted. So my scribe starting sequence is to copy the current messages file to a new beforeboot.log file, write a "Start boot" to a new messages file; then copy the current syslog.log to a startup.log file, start syslog-ng, and then as the very first thing process the startup.log file with a timestamp of when it is processed. At that point the startup.log file is about 1200 lines. If ntp has synced, I end up with a beforeboot.log file, and a messages file that starts with "Start boot" and then all the logged messages generated from the boot on, with a current timestamp. So I can see other scripts waiting.
I sort of vaguely assumed that entware didn't start until ntp syncs, but I see that a more than a few addons have ntp checks. I get that if ntp has synced the addon will immediately go on its merry way, but some wait 30 seconds for the next check, I think. So there could be several addons waiting during the boot process before they actually start.
So I'm wondering if there should be a straight off single check/wiat for all the addons, and where in the hooks it should be. Or, maybe there is?
TL;DR
The standard scribe install appends the starting log to the messages file. I like to see the messages file as a single file with the current boot and a proper timestamp. I never feel the need to go back to older messages files, but I do want to see what might have been logged before the router rebooted. So my scribe starting sequence is to copy the current messages file to a new beforeboot.log file, write a "Start boot" to a new messages file; then copy the current syslog.log to a startup.log file, start syslog-ng, and then as the very first thing process the startup.log file with a timestamp of when it is processed. At that point the startup.log file is about 1200 lines. If ntp has synced, I end up with a beforeboot.log file, and a messages file that starts with "Start boot" and then all the logged messages generated from the boot on, with a current timestamp. So I can see other scripts waiting.