From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Wed, 15 Oct 2008 10:28:13 +0200
From: Christian Kellermann <Christian.Kellermann@nefkom.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Message-ID: <20081015082813.GD1296@hermes.my.domain>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="/unnNtmY43mpUSKx"
Content-Disposition: inline
User-Agent: Mutt/1.5.16 (2007-06-09)
Subject: [9fans] How to get the diagnostics of fs(3)
Topicbox-Message-UUID: 1e5a1dba-ead4-11e9-9d60-3106f5b1d025


--/unnNtmY43mpUSKx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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

--=20
You may use my gpg key for replies:
pub  1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)

--/unnNtmY43mpUSKx
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (OpenBSD)

iEYEARECAAYFAkj1qZwACgkQXYob3Uf3l4jTgACgqM/stFqstLrwbakWNJoOv8Qt
Ug0AmgN2ZduCKsmK1+MLEkzHT7vVThiF
=X48t
-----END PGP SIGNATURE-----

--/unnNtmY43mpUSKx--