-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systeminfo-time showing strangly high values #20
Comments
It was fine in v0.15.0-9-g2f559fb and maybe later. |
Hi,
we had a fix about this in v0.15.1-100-ga1a4c7e4, can you test the most
recent "develop" branch?
Henning
…On Mon, Nov 12, 2018 at 5:43 PM pocki80 ***@***.***> wrote:
It was fine in v0.15.0-9-g2f559fb and maybe later.
Is was not ok in v0.15.1-75-g312d09d or maybe earlier.
So some commit between these two screwed it up.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AG8Ytx1lVcEPlrPuXpVL4Z95qKgk6gyuks5uuaF2gaJpZM4YZ_Cx>
.
|
Actually no, I was not able to test it until now. But looking at the code changes it seems to be fixed. |
Sorry,
I have been tracking a problem in the main netlink code for weeks... I
don't want to merge before this is done because it tends to break the
routing agent in my special test setup... I am lucky I found a way to
trigger it reliable.
…On Fri, Nov 30, 2018 at 9:45 AM pocki80 ***@***.***> wrote:
Actually no, I was not able to test it until now. But looking at the code
changes it seems to be fixed.
Though, waiting for all these recent commits to get merged to master.
BR
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#20 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AG8Yt_MtbFOQPEZkWBHLMke2hnAPJzojks5u0PAogaJpZM4YZ_Cx>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
using telnet plugin "systeminfo time" I see that the uptime second counter increases in an unexpected fast was. As there war "seconds since deamon start" in former versions, I looks like this right now:
The text was updated successfully, but these errors were encountered: