IRC.

1 files changed, 27 insertions, 0 deletions

diff --git a/open_issues/syslog.mdwn b/open_issues/syslog.mdwn
index 5fec38b1..2e902698 100644
--- a/open_issues/syslog.mdwn
+++ b/open_issues/syslog.mdwn
@@ -43,3 +43,30 @@ IRC, freenode, #hurd, 2011-08-08
     < youpi> shm should work with the latest libc
     < youpi> what won't is sysv sem
     < youpi> (i.e. semget)
+
+
+IRC, OFTC, #debian-hurd, 2011-11-02:
+
+    * pinotree sighs at #645790 :/
+    <tschwinge> pinotree: W.r.t. 645790 -- yeah, ``someone'' should finally
+      figure out what's going on with syslog.
+      http://lists.gnu.org/archive/html/bug-hurd/2008-07/msg00152.html
+    <tschwinge> pinotree: And this...
+      http://lists.gnu.org/archive/html/bug-hurd/2007-02/msg00042.html
+    <pinotree> tschwinge: i did that 20 invocations tests recently, and
+      basically none of them has been logged
+    <pinotree> tschwinge: when i started playing with logger more, as result i
+      had some server that started taking all the cpu, followed by other
+      servers and in the end my ssh connection were dropped and i had nothing
+      to do (not even login from console)
+    <tschwinge> pinotree: Sounds like ``fun''.  Hopefully we can manage to
+      understand (and fix the underlying issue) why a simple syslog()
+      invocation can make the whole system instable.
+    <pinotree> tschwinge: to be honest, i got havoc in the system when i told
+      syslog to manually look for /dev/log (-u /dev/log), possibly alao when
+      telling to use a datagram socket (-d)
+    <pinotree> but even if a normal syslog() invocation does not cause havoc,
+      there's still the "lost messages" issue
+    <tschwinge> Yep.  What I've been doing ever since, is deinstall all
+      *syslog* packages.
+    <tschwinge> This ``fixed'' all syslog() hangs.