[9fans] How to get the diagnostics of fs(3)

["Fco. J. Ballesteros" <nemo@lsub.org>]

We use aux/clog to send the contents of /dev/kprint to /sys/log/$sysname
We bind '#k' by hand after booting our server, but how you do it it depends
on the particular config for your machine.

>  From: Christian.Kellermann@nefkom.net
>  To: 9fans@cse.psu.edu
>  Reply-To: 9fans@9fans.net
>  Date: Wed Oct 15 10:31:41 CET 2008
>  Subject: [9fans] How to get the diagnostics of fs(3)
>
>  Dear List,
>
>  I have experienced a disk crash in a mirrored fs(3). It turned out
>  that the mirroring has not been successful since December 2007 which
>  is quite a loss for me now.
>
>  To prevent a case like this it would have helped If I had seen the
>  error messages by fs(3) earlier/at all. By browsing through the
>  code with the intention to add somehting there I found several
>  prints that do issue the right warnings. What I don't see at the
>  moment: Where do they go to? How is #k started and how can I redirect
>  the stdout of #k to a file that I can monitor?
>
>  Thanks for your insights,
>
>  Christian
>
>  --
>  You may use my gpg key for replies:
>  pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)
>
>
>  — 2
>