Re: Bug#33993: general: Should log all the boot messages
On Fri, Aug 18, 2000 at 12:28:58AM +0200, Peter Palfrader wrote: dmesg only is for kernel messages. The entire userland (like starting daemons etc.) is not covered by it. IIRC a few months ago someone had a patch agains init (or something else) that would log the entire startup. I don't know what its current status is but it seemed like a really nice idea at that time. This patch was written by one of my classmates. I told him to file a bug against shellutils, or to write to the maintainer, but I don't know if he finally did. The source is available for download in http://pusa.uv.es/~ulisses/debian-rc. I guess I can post a diff against the package in the BTS, if Mike wants one. Ulisses can be reached at [EMAIL PROTECTED] He will be glad to hear some news about this. Jordi -- Jordi Mallach Pérez || [EMAIL PROTECTED] || Rediscovering Freedom, aka Oskuro in|| [EMAIL PROTECTED] || Using Debian GNU/Linux Reinos de Leyenda || [EMAIL PROTECTED] || http://debian.org http://sindominio.net GnuPG public information: pub 1024D/917A225E telnet pusa.uv.es 23 73ED 4244 FD43 5886 20AC 2644 2584 94BA 917A 225E pgpJCFc5LyNfs.pgp Description: PGP signature
Re: Bug#33993: general: Should log all the boot messages
In article [EMAIL PROTECTED], Colin Watson [EMAIL PROTECTED] wrote: Decklin Foster [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: Cesar Eduardo Barros [EMAIL PROTECTED] writes: There are too many boot messages, and they sometimes scroll too fast. It would be nice to log all the output from the boot scripts. Huh? does dmesg not do what you want? dmesg doesn't log the output from init.d scripts. (I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).) Have a look at bootlogd from sysvinit. It isn't installed by default since it's not quite finished yet, but I think it does what you want. It captures all screen output while booting and keeps it in memory until it is able to write to /var/log/boot.log. Needs no special support, hacked scripts etc. The reason that it isn't used yet is that I'm not sure it actually is a good idea - it wouldn't work with a 'pretty startup' like RedHat has, for example. I'm not quite sure what exactly the best way to solve this is. Most probably extending /etc/init.d/rc and /etc/init.d/rcS, which need a rewrite anyway to get merged into 1 script. But we do need some way to store the messages produced when the root filesystem is still read only and/or /var isn't mounted yet. So it's not a trivial problem. Mike. -- en daarom zoeken wij voor de uitbreiding van de it-afdeling een vrolijke, hard werkende, enthousiaste systeembeheerder! lijkt dit je wat, reageer dan nu! -- marleen in nl.susy
Re: Bug#33993: general: Should log all the boot messages
On Thu 17 Aug 2000, Colin Watson wrote: dmesg doesn't log the output from init.d scripts. (I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).) Or shift-PageUp However, sometimes I have wished that the init.d messages were in fact logged somewhere. E.g. after a day you notice something isn't running, and you wonder whether there was some message from the init.d script. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Re: Bug#33993: general: Should log all the boot messages
On Fri, Aug 18, 2000 at 10:20:48AM +0200, Paul Slootman wrote: On Thu 17 Aug 2000, Colin Watson wrote: dmesg doesn't log the output from init.d scripts. (I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).) Or shift-PageUp Of course, if you run a display manager, you lose your scroll back as soon as the X server starts... -- G. Branden Robinson |To be is to do -- Plato Debian GNU/Linux|To do is to be -- Aristotle [EMAIL PROTECTED] |Do be do be do -- Sinatra http://www.debian.org/~branden/ | pgp4eR74yzTVk.pgp Description: PGP signature
Re: Bug#33993: general: Should log all the boot messages
On Fri 18 Aug 2000, Branden Robinson wrote: On Fri, Aug 18, 2000 at 10:20:48AM +0200, Paul Slootman wrote: On Thu 17 Aug 2000, Colin Watson wrote: (I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).) Or shift-PageUp Of course, if you run a display manager, you lose your scroll back as soon as the X server starts... True, which is why I'd like the log. I noted the shift-PageUp in response to the ctrl-s suggestion; I'm usually too slow with the ctrl-s, but then shift-PageUp helps. And I usually start xdm by hand anyway :-) That used to be the safest way, although the new code (well, new since a long time) to prevent looping when the X config is wrong works very well. Paul Slootman -- home: [EMAIL PROTECTED] http://www.wurtel.demon.nl/ work: [EMAIL PROTECTED] http://www.murphy.nl/ debian: [EMAIL PROTECTED] http://www.debian.org/ isdn4linux: [EMAIL PROTECTED] http://www.isdn4linux.de/
Bug#33993: general: Should log all the boot messages
Decklin Foster writes (Bug#33993: general: Should log all the boot messages): Cesar Eduardo Barros [EMAIL PROTECTED] writes: Package: general Version: N/A Severity: wishlist There are too many boot messages, and they sometimes scroll too fast. It would be nice to log all the output from the boot scripts. Huh? does dmesg not do what you want? Dmesg catches the actual kernel messages, but it doesn't catch the whole boot process---most particularly, it doesn't get all the output of the /etc/init.d scripts that are run (and some of those errors are important). I've been annoyed by it a few times, since my machine boots very quickly, and usually xdm starts before I can read some of the last messages (and then since the VT has changed, the scrollback is lost). -- Richard W Kaszeta PhD. Candidate and Sysadmin [EMAIL PROTECTED] University of MN, ME Dept http://www.menet.umn.edu/~kaszeta
Bug#33993: general: Should log all the boot messages
Cesar Eduardo Barros [EMAIL PROTECTED] writes: Package: general Version: N/A Severity: wishlist There are too many boot messages, and they sometimes scroll too fast. It would be nice to log all the output from the boot scripts. Huh? does dmesg not do what you want? -- There is no TRUTH. There is no REALITY. There is no CONSISTENCY. There are no ABSOLUTE STATEMENTS. I'm very probably wrong. -- BSD fortune(6)
Re: Bug#33993: general: Should log all the boot messages
Decklin Foster [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: Cesar Eduardo Barros [EMAIL PROTECTED] writes: There are too many boot messages, and they sometimes scroll too fast. It would be nice to log all the output from the boot scripts. Huh? does dmesg not do what you want? dmesg doesn't log the output from init.d scripts. (I usually recommend Ctrl-S (stop output) and Ctrl-Q (restart output).) -- Colin Watson [EMAIL PROTECTED]
Bug#33993: general: Should log all the boot messages
On Thu, 17 Aug 2000, Decklin Foster wrote: Cesar Eduardo Barros [EMAIL PROTECTED] writes: Package: general Version: N/A Severity: wishlist There are too many boot messages, and they sometimes scroll too fast. It would be nice to log all the output from the boot scripts. Huh? does dmesg not do what you want? dmesg only is for kernel messages. The entire userland (like starting daemons etc.) is not covered by it. IIRC a few months ago someone had a patch agains init (or something else) that would log the entire startup. I don't know what its current status is but it seemed like a really nice idea at that time. yours, peter -- PGP encrypted messages preferred. http://www.cosy.sbg.ac.at/~ppalfrad/ [please CC me on lists]
