From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@9fans.net From: "Fco. J. Ballesteros" Date: Wed, 15 Oct 2008 11:13:04 +0200 In-Reply-To: <20081015084718.GE1296@hermes.my.domain> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: Re: [9fans] How to get the diagnostics of fs(3) Topicbox-Message-UUID: 1e6e70bc-ead4-11e9-9d60-3106f5b1d025 All the output sent to the console is available via /dev/kprint. If you copy that file somewhere, eg, using aux/clog, all your messages should be in that file. > From: Christian.Kellermann@nefkom.net > To: 9fans@9fans.net > Reply-To: 9fans@9fans.net > Date: Wed Oct 15 10:48:09 CET 2008 > Subject: Re: [9fans] How to get the diagnostics of fs(3) > > * Fco. J. Ballesteros [081015 10:42]: > > 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. > > > > As it has been I placed the fs= line in plan9.ini as I had my > fossil/venti starting off the fs(3) server. This might not be a > good idea now. Still if you want to keep it this way, can I still > get to the output? > > > > — 2 >