path: root/service_solahart_jakarta_selatan__082122541663/gnumach_rpc_timeouts.mdwn
diff options
Diffstat (limited to 'service_solahart_jakarta_selatan__082122541663/gnumach_rpc_timeouts.mdwn')
1 files changed, 19 insertions, 0 deletions
diff --git a/service_solahart_jakarta_selatan__082122541663/gnumach_rpc_timeouts.mdwn b/service_solahart_jakarta_selatan__082122541663/gnumach_rpc_timeouts.mdwn
new file mode 100644
index 00000000..68cfcb5a
--- /dev/null
+++ b/service_solahart_jakarta_selatan__082122541663/gnumach_rpc_timeouts.mdwn
@@ -0,0 +1,19 @@
+[[!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
+[[!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