IRC.

1 files changed, 37 insertions, 2 deletions

diff --git a/open_issues/syslog.mdwn b/open_issues/syslog.mdwn
index 2e902698..19cba82e 100644
--- a/open_issues/syslog.mdwn
+++ b/open_issues/syslog.mdwn
@@ -1,4 +1,19 @@
-IRC, unknwon channel, unknown date.
+[[!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
+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_hurd]]
+
+[[!toc]]
+
+# IRC, unknown channel, unknown date
 
     <tschwinge> scolobb: In wiki edit 60accafa79f645ae61b578403f7fc0c11914b725
       I see that you intend(ed) to use syslog for logging debug messages.  I
@@ -16,7 +31,7 @@ IRC, unknwon channel, unknown date.
       doesn't help if I restart syslogd).
 
 
-IRC, freenode, #hurd, 2011-08-08
+# IRC, freenode, #hurd, 2011-08-08
 
     < pinotree> wow, `logger` + a simple C udp server can cause havoc
     < pinotree> youpi: ever seen something like
@@ -70,3 +85,23 @@ IRC, OFTC, #debian-hurd, 2011-11-02:
     <tschwinge> Yep.  What I've been doing ever since, is deinstall all
       *syslog* packages.
     <tschwinge> This ``fixed'' all syslog() hangs.
+
+
+# IRC, freenode, #hurd, 2012-03-28
+
+    <braunr> i can see lots of CRON processes hanging around
+    <braunr> pinotree: crontab -l was hanging too when trying to quickly see
+      what went wrong
+    <braunr> so it may be an unreleased lock of some kind
+    <antrik> braunr: do you have syslog installed by any chance?...
+    <antrik> IIRC that bug has never been fixed :-(
+    <braunr> yes syslogd is running
+    <antrik> that's probably the culprit then
+    <braunr> ok
+    <braunr> i'll just disable it for now then
+    <antrik> the error has existed for years
+    <antrik> was similar for me though: for a long time I have been hearing
+      about this issue, and only suddenly I started experiencing it myself...
+    <antrik> it depends on how many things are actually logged. IIRC the hang
+      happens when some client sends 128 messages to syslog or something like
+      that