Am Don, 2002-09-26 um 08.25 schrieb Ryan Cumming:
> Before I go again, any suggestions on how to reliably capture these error=
=20
> messages? Because the filesystem goes read-only immediately,=20
> /var/log/messages is hardly useful.
Indeed, but I'd wonder why someone whould start syslogd on a r/o
filesystem, so probably /var/log/messages is not used at this time
anyway. You could set up syslogd to do remote logging to another machine
and fire it up before the troubles to capture anything. But of course
this requires
a) another machine
b) syslog set up on both sides for remote logging
c) a working network
An alternative would be to mount another disk with a different
filesystem (reiserfs/FAT) and log to there.
=20
--=20
Servus,
Daniel
--=-fuuuFtzIEE9xrpcD7xQF
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQA9ku6Mchlzsq9KoIYRAsb7AJ0X6Dc9ae4jSOpO+TcFROGkkLNn5gCfSVNn
fVjobZ7x0HrwFhf1T2aYuKw=
=8ANO
-----END PGP SIGNATURE-----
--=-fuuuFtzIEE9xrpcD7xQF--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/