View Single Post
Old 07-12-2013, 12:41 PM   #19
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 7,026
Karma: 6359394
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by nasser View Post
Will running 'dmesg|more' under kterm do the same thing?
I tried.. there's a LOT of info.. which are the lines which tell the state it's restarting from?
The way the button does it (you can just read the script if you want):

1) dmesg -c > tempfile -> rename tempfile to date/time titled document.
(The '-c' clears the message buffer after outputting it.)

I.E:
press button before desired action dump
press button after desired action

The second document (later date/timestamp) will have only the messages *after* the first document.

That is: You could (later) cat the two together if you wanted both in one document file.

I did it that way because the most common use case is to capture only the things before/after a specific **something**.
knc1 is offline   Reply With Quote