summaryrefslogtreecommitdiff
path: root/open_issues/pfinet_vs_system_time_changes.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/pfinet_vs_system_time_changes.mdwn')
-rw-r--r--open_issues/pfinet_vs_system_time_changes.mdwn31
1 files changed, 25 insertions, 6 deletions
diff --git a/open_issues/pfinet_vs_system_time_changes.mdwn b/open_issues/pfinet_vs_system_time_changes.mdwn
index 46705047..09b00d30 100644
--- a/open_issues/pfinet_vs_system_time_changes.mdwn
+++ b/open_issues/pfinet_vs_system_time_changes.mdwn
@@ -11,14 +11,16 @@ License|/fdl]]."]]"""]]
[[!tag open_issue_hurd]]
-IRC, unknown channel, unknown date.
+
+# IRC, unknown channel, unknown date
<grey_gandalf> I did a sudo date...
<grey_gandalf> and the machine hangs
-This was very likely a misdiagnosis:
+This was very likely a misdiagnosis.
+
-IRC, freenode, #hurd, 2011-03-25:
+# IRC, freenode, #hurd, 2011-03-25
<tschwinge> antrik: I suspect it'S some timing stuff in pfinet that perhaps
uses absolute time, and somehow wildely gets confused?
@@ -42,7 +44,8 @@ IRC, freenode, #hurd, 2011-03-25:
wrap-around, and thus the same result.)
<tschwinge> Yes.
-IRC, freenode, #hurd, 2011-10-26:
+
+# IRC, freenode, #hurd, 2011-10-26
<antrik> anyways, when ntpdate adjusts to the past, the connections hang,
roughly for the amount of time being adjusted
@@ -50,7 +53,8 @@ IRC, freenode, #hurd, 2011-10-26:
<antrik> (well, if it's long enough, they probably timeout on the other
side...)
-IRC, freenode, #hurd, 2011-10-27:
+
+# IRC, freenode, #hurd, 2011-10-27
<antrik> oh, another interesting thing I observed is that the the subhurd
pfinet did *not* drop the connection... only the main Hurd one. I thought
@@ -60,7 +64,8 @@ IRC, freenode, #hurd, 2011-10-27:
where I set the date is affected, and not the pfinet in the other
instance
-IRC, freenode, #hurd, 2012-06-28:
+
+# IRC, freenode, #hurd, 2012-06-28
<bddebian> great, now setting the date/time fucked my machine
<pinotree> yes, we lack a monotonic clock
@@ -80,3 +85,17 @@ IRC, freenode, #hurd, 2012-06-28:
it fucked me because I now cannot get to it.. :)
<antrik> bddebian: that's odd... you should be able to just log in again
IIRC
+
+
+# IRC, freenode, #hurd, 2012-07-29
+
+ <antrik> pfinet can't cope with larger system time changes because it can't
+ use a monotonic clock
+
+[[clock_gettime]].
+
+ <braunr> well when librt becomes easily usable everywhere (it it's
+ possible), it will be quite easy to work around this issue
+ <pinotree> yes and no, you just need a monotonic clock and clock_gettime
+ able to use it
+ <braunr> why "no" ?