Your message dated Thu, 06 Oct 2011 15:41:47 +0200
with message-id <[email protected]>
and subject line not reproducible
has caused the Debian Bug report #357345,
regarding syslog-ng: /dev/xconsole empty
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
357345: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357345
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: syslog-ng
Version: 1.9.9-1
Severity: normal
I update syslog-ng to last version, but the first time using
#cat /dev/xconsole
It is fine show me the info that send to syslog, i'm logout
the system, relogin.
I try use:
#cat /dev/xconsole
again to see info, but this is empty and syslog-ng not send
nothing.
To fix i need restart the daemond for work again.
sorry my english is bad =).
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=es_MX.UTF-8, LC_CTYPE=es_MX.UTF-8 (charmap=UTF-8)
Versions of packages syslog-ng depends on:
ii libc6 2.3.5-13 GNU C Library: Shared libraries an
ii util-linux 2.12r-6 Miscellaneous system utilities
Versions of packages syslog-ng recommends:
ii logrotate 3.7.1-2 Log rotation utility
-- no debconf information
--- End Message ---
--- Begin Message ---
This report is a good few years old, and received no more information
after the initial report, and I know of no similar issues in recent
versions.
I believe the original problem wasn't actually a problem in syslog-ng,
but merely an oversight on the users part: cat /dev/xconsole will empty
the buffer, and will not display past entries when invoked again.
Thus, logging out and back in, and doing a cat /dev/xconsole results in
nothing, because the pipe's empty. The reason messages appear
afterwards, is because syslog-ng generated messages that were routed
towards xconsole, for one reason or the other.
Anyway, I'm closing this bug on the grounds that it's five years old,
and was not reproducible even back then, nor is it reproducible now.
--
|8]
--- End Message ---
