Open
Conversation
|
Oh I'd missed this last week. Sorry about that. I've put it on my list to test. I am afraid though, that I will only get round to this next week Tuesday. |
|
Good news. Works great! Apart from the log, I observed the datetime chainging appropriately. |
rhbvkleef
approved these changes
Mar 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I think another (more generic) approach to fix issue #15
and probably #11
I switched the date invocation from passing a formatted ISO string to passing epoch seconds: date -u -s "@". I also added a parse check to ensure the incoming ISO timestamp is valid before converting to epoch seconds.
This command is afaik compatible with busybox, so no detection or something is necessary.
@rhbvkleef could you please verify?