summaryrefslogtreecommitdiff
path: root/open_issues/gnumach_rpc_timeouts.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/gnumach_rpc_timeouts.mdwn')
-rw-r--r--open_issues/gnumach_rpc_timeouts.mdwn19
1 files changed, 0 insertions, 19 deletions
diff --git a/open_issues/gnumach_rpc_timeouts.mdwn b/open_issues/gnumach_rpc_timeouts.mdwn
deleted file mode 100644
index 68cfcb5a..00000000
--- a/open_issues/gnumach_rpc_timeouts.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!meta copyright="Copyright © 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
-document under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no Invariant
-Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
-is included in the section entitled [[GNU Free Documentation
-License|/fdl]]."]]"""]]
-
-[[!tag open_issue_gnumach]]
-
-
-# IRC, freenode, #hurd, 2012-04-28
-
- <pinotree> uhm, apparently mach cannot handle timeouts for rpc's of more
- than (2^(sizeof(mach_msg_timeout_t) * 8) - 1) / HZ
- <pinotree> it seems that how ticks are calculated in mach, it becomes 0
- <pinotree> +because of