From:
[email protected]
On Sat, Aug 14, 2004 at 06:34:02PM +0200, Robert Millan wrote:
On Sat, Aug 14, 2004 at 06:05:20PM +0200, Marc Haber wrote:
On Sat, Aug 14, 2004 at 05:38:45PM +0200, Robert Millan wrote:
On Fri, Aug 13, 2004 at 08:58:37PM +0200, Marc Haber wrote:
On Fri, Aug 13, 2004 at 09:48:12AM -0700, Debian Bug Tracking System wrote:
What gnu syslogd does is reading from where _PATH_KLOG points to, which is the
portable way of obtaining kernel logs.
That should be documented in the manpage.
It is:
"Syslogd reads messages from [...], and from the special device /dev/klogd
(to read kernel messages)"
Since this neither includes /proc/kmsg, nor any reference to
_PATH_KLOG, you're obviously making fun of me, or are not really
interested in making the package any easier to use. Thanks a lot for wasting my time.
I made a mistake and asssumed _PATH_KLOG would point to /dev/klog on linux-gnu, which is not correct. This is the most obvious explanation to
my wrong response. What kind of reasoning did you follow to reach the conclussion that I'm making fun of you?
Well, I asked to document A, and you pointed me towards documentation
that looks like documenting A, conveniently leaving out the part that
cleanly shows that the documentation I asked for is actually not there.
Apparently, you think that harrassing maintainers like this will help
you solve the actual problem, but in practice, it doesn't.
If you think that being annoyed from being pointed to non-fitting docs
and reacting appropriately is harrassment, I cannot find the right
words to comment.
Now, send me a patch to dynamicaly generate the manpage with the
value contained in _PATH_KLOG.
Just refering to _PATH_KLOG in the man page would be enough. People
can be expecte to pull that path from the sources. If they know what
to search for (which they currently don't, and which they would if
_PATH_KLOG were referenced in the man page).
btw, klogd(8) from the sysklogd package nicely explains how things are
for Linux:
In Linux there are two potential sources of kernel log information: the
/proc file system and the syscall (sys_syslog) interface, although
ultimately they are one and the same. Klogd is designed to choose
whichever source of information is the most appropriate. It does this
by first checking for the presence of a mounted /proc file system. If
this is found the /proc/kmsg file is used as the source of kernel log
information. If the proc file system is not mounted klogd uses a sys-
tem call to obtain kernel messages. The command line switch (-s) can
be used to force klogd to use the system call interface as its messag-
ing source.
Greetings
Marc
-- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Karlsruhe, Germany | lose things." Winona Ryder | Fon: *49 721 966 32 15 Nordisch by Nature | How to make an American Quilt | Fax: *49 721 966 31 29
--
To UNSUBSCRIBE, email to
[email protected]
with a subject of "unsubscribe". Trouble? Contact
[email protected]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)