Timeline for Pipe kernel messages to another process as they occur
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 1, 2014 at 20:42 | history | edited | Lesmana | CC BY-SA 3.0 |
added 19 characters in body
|
| Apr 13, 2011 at 21:12 | comment | added | Lesmana |
@TuxRug I messed up. It should have been /var/log/messages instead of /var/log/dmesg. I updated my answer. Also, with tail -n 0 you only get the newestest messages after invocation of the command.
|
|
| Apr 13, 2011 at 21:10 | history | edited | Lesmana | CC BY-SA 3.0 |
added 3 characters in body; added 5 characters in body
|
| Apr 13, 2011 at 20:50 | comment | added | TuxRug | This doesn't push them as they happen, though, and I only want the ones that just fired to display. I want something that catches the messages as they are produced. | |
| Apr 13, 2011 at 20:12 | history | answered | Lesmana | CC BY-SA 3.0 |