summaryrefslogtreecommitdiff
path: root/open_issues/pfinet_vs_system_time_changes.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2012-07-11 22:39:59 +0200
committerThomas Schwinge <tschwinge@gnu.org>2012-07-11 22:39:59 +0200
commit8cee055ec4fac00e59f19620ab06e2b30dccee3c (patch)
tree6cd7ca1b8ce7eba1820fdbd31ee5755ed33dabe2 /open_issues/pfinet_vs_system_time_changes.mdwn
parentb75e038615d51cb62c200e336e59202519db8cae (diff)
IRC.
Diffstat (limited to 'open_issues/pfinet_vs_system_time_changes.mdwn')
-rw-r--r--open_issues/pfinet_vs_system_time_changes.mdwn24
1 files changed, 23 insertions, 1 deletions
diff --git a/open_issues/pfinet_vs_system_time_changes.mdwn b/open_issues/pfinet_vs_system_time_changes.mdwn
index 513cbc73..46705047 100644
--- a/open_issues/pfinet_vs_system_time_changes.mdwn
+++ b/open_issues/pfinet_vs_system_time_changes.mdwn
@@ -1,4 +1,5 @@
-[[!meta copyright="Copyright © 2010, 2011 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2010, 2011, 2012 Free Software Foundation,
+Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -58,3 +59,24 @@ IRC, freenode, #hurd, 2011-10-27:
<antrik> it's really fascinating that only the pfinet on the Hurd instance
where I set the date is affected, and not the pfinet in the other
instance
+
+IRC, freenode, #hurd, 2012-06-28:
+
+ <bddebian> great, now setting the date/time fucked my machine
+ <pinotree> yes, we lack a monotonic clock
+ <pinotree> there are select() loops that use gettimeofday to determine how
+ much time to wait
+ <pinotree> thus if the time changes (eg goes back), the calculation goes
+ crazy
+ <antrik> pinotree: didn't you implement a monotonic clock?...
+ <pinotree> started to
+ <antrik> bddebian: did it really fuck the machine? normally it only resets
+ TCP connections...
+ <pinotree> yeah, i remember such gettimeofay-based select-loops at least in
+ pfinet
+ <antrik> I don't think it's a loop. it just drops the connections,
+ believing they have timed out
+ <bddebian> antrik: Well in this case I don't know because I am at work but
+ 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