summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2014-03-06 18:12:57 +0000
committerGravatar admin <admin@branchable.com>2014-03-06 18:12:57 +0000
commitb7732643bfc16fb2965cf61a89235a1d2de189c4 (patch)
treec9cecf46b44b765defb0dd8c153612137e424550
parent98ceb92bc1644be2acdc2d1a0f60f25310908dde (diff)
Added a comment
-rw-r--r--doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_5_6b9b87bfb8b94171b3dba51919fd1ceb._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_5_6b9b87bfb8b94171b3dba51919fd1ceb._comment b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_5_6b9b87bfb8b94171b3dba51919fd1ceb._comment
new file mode 100644
index 000000000..d612cf35f
--- /dev/null
+++ b/doc/bugs/Assistant_lost_dbus_connection_spamming_log/comment_5_6b9b87bfb8b94171b3dba51919fd1ceb._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.146"
+ subject="comment 5"
+ date="2014-03-06T18:12:57Z"
+ content="""
+Again the accept message does not seem to be related to dbus. A dbus client has no reason to do that; a web server does. The use of `O_NONBLOCK` with accept4 seems likely to be the culprit to me.
+
+How frequently is dbus mentioned in the log?
+"""]]