slacky.eu

E' possibile fare in modo che i messaggi in dmesg se ne vadano a finire in un file in var/log ?
Se ricordo bene al boot viene dato un comando che scrive tutto in boot.log, ma si ferma dal momento del boot a quel momento; tutti i log successivi vengono persi.
Utile sarebbe anche che a tale file venga aggiunta davanti la data (visto che il dmesg normale non ce l'ha e sarebbe un bel po' utile).

In particolare uso redhat, ma mi sembra che anche slackware non abbia il dmesg replicato in /var/log.

dmesg in Slackware esiste come file. Se non ricordo male /var/log/syslog e messages contengono, divisi, gli stessi dati di dmesg.
Per /var/log/dmesg in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=719398
Per la data: http://linuxaria.com/article/how-to-mak ... le?lang=it e http://cateee.net/lkddb/web-lkddb/PRINTK_TIME.html e ancora: http://ubuntuforums.org/showthread.php?t=1499412

dmesg -T

@shuren: grazie, appena posso do una occhiata a quei link.
@conraid: man dmesg di redhat:

Codice: Seleziona tutto

DMESG(8)                                                              DMESG(8)

NAME
       dmesg - print or control the kernel ring buffer

SYNOPSIS
       dmesg [ -c ] [ -n level ] [ -s bufsize ]

DESCRIPTION
       dmesg is used to examine or control the kernel ring buffer.

       The  program  helps  users to print out their bootup messages.  Instead of copying the messages by hand, the user
       need only:
              dmesg > boot.messages
       and mail the boot.messages file to whoever can debug their problem.

OPTIONS
       -c     Clear the ring buffer contents after printing.

       -sbufsize
              Use a buffer of size bufsize to query the kernel ring buffer.  This is 16392  by  default.   (The  default
              kernel syslog buffer size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.)  If you have set the
              kernel buffer to be larger than the default then this option can be used to view the entire buffer.

       -nlevel
              Set the level at which logging of messages is done to the console.  For example, -n 1  prevents  all  mes-
              sages,  expect panic messages, from appearing on the console.  All levels of messages are still written to
              /proc/kmsg, so syslogd(8) can still be used to control exactly where kernel messages appear.  When the  -n
              option is used, dmesg will not print or clear the kernel ring buffer.

              When both options are used, only the last option on the command line will have an effect.

SEE ALSO
       syslogd(8)

edit: slackware util-linux=2.21; redhat util-linux=2.13

slacky.eu

output del dmesg in var/log

output del dmesg in var/log

Re: output del dmesg in var/log

Re: output del dmesg in var/log

Re: output del dmesg in var/log