|author||Thomas Schwinge <firstname.lastname@example.org>||2012-08-07 23:25:26 +0200|
|committer||Thomas Schwinge <email@example.com>||2012-08-07 23:25:26 +0200|
Diffstat (limited to 'open_issues/wait_errors.mdwn')
1 files changed, 25 insertions, 0 deletions
diff --git a/open_issues/wait_errors.mdwn b/open_issues/wait_errors.mdwn
new file mode 100644
@@ -0,0 +1,25 @@
+[[!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_glibc open_issue_hurd]]
+# IRC, freenode, #hurd, 2012-07-12
+ <braunr> tschwinge: have you encountered wait() errors ?
+ <tschwinge> What kind of wait errors?
+ <braunr> when running htop or watch vmstat, other apparently unrelated
+ processes calling wait() sometimes fail with an error
+ <braunr> i saw it mostly during builds, as they spawn lots of children
+ <braunr> (and used the aforementioned commands to monitor the builds)
+ <tschwinge> Sounds nasty... No, don't remember seeing that. But I don't
+ typiclly invoke such commands during builds.
+ <tschwinge> So this wait thing suggests there's something going wrong in
+ the proc server?
+ <braunr> tschwinge: yes