Re: dmesg.log
Hi,
Sorry for being late with my answer.
In Knoppix, I try to avoid automatic logging to files on the ramdisk,
because these can get huge and crash your computer if it runs out of
memory. /var/log/syslog can quickly grow over 1GB when some service
keeps restarting itself because of errors, or, for example, if you turn
on logging network packages via iptables.
For these reasons, the autostarted syslogd on Knoppix uses
/etc/syslog-knoppix.conf if present, which logs everything to virtual
console number 12 instead of files in /var/log/. The boot status message
showing up when syslog starts actually mentions this, but it probably
goes away again too fast to be readable.
If you made a USB flashdisk for booting, you can delete
/etc/syslog-knoppix.conf to restore the original behaviour of logging to
files in /var/log.
Regards
-Klaus
On Mon, Oct 25, 2010 at 11:05:22AM -0800, jonr@destar.net wrote:
> Quoting stirner <bmax@gmx.it>:
> >
> >jonr wrote:
> >>
> >>Quoting stirner <bmax@gmx.it>:
> >>
> >>>
> >>>
> >>>
> >>>jonr wrote:
> >>>>
> >>>>Hello Knoppix List!
> >>>>
> >>>>I am new to the list and hope you can help me with an issue I am
> >>>>having. I am using Knoppix 6.2 and I need the full output of dmesg for
> >>>>another issue that I am having.
> >>>>
> >>>>When I run dmesg it is truncated and not showing me the full output
> >>>>and I don't see it in /var/log/. Is there a way to get the full
> >>>>output, such as the dmesg.log file, for the 6.2 version?
> >>>>
> >>>>Any help is greatly appreciated,
> >>>>
> >>>>Jon
> >>>>
> >>>>
> >>>>
> >>>>--
> >>>>To UNSUBSCRIBE, email to debian-knoppix-request@lists.debian.org
> >>>>with a subject of "unsubscribe". Trouble? Contact
> >>>>listmaster@lists.debian.org
> >>>>Archive:
> >>>>[🔎] 20101022172007.133261a0d0op2w84@mail.destar.net">http://lists.debian.org/[🔎] 20101022172007.133261a0d0op2w84@mail.destar.net
> >>>>
> >>>>
> >>>>
> >>>
> >>>Try with dmesg|less
> >>>
> >>>You have all the log in /var/logs/ ( cat /var/log/debug |less or cat
> >>>/var/log/messages |less )
> >>>
> >>>Don't forget cat /home/knoppix/.xsession-errors for debbugging X
> >>>applications.
> >>>
> >>>Cheers
> >>>
> >>>Max
> >>>--
> >>
> >>Hello Max,
> >>
> >>Thats what I thought as well but there is no debug log in /var/log and
> >>no messages in /var/log/. When I do dmesg|less the dmesg log is
> >>truncated and I miss most of it. I wanted to put a kernel option on
> >>the boot line, log_buf_len=262144, but there was no way to do that as
> >>far as I could see.
> >>
> >>I could be missing something but I am not sure what.
> >>
> >>Thanks for the reply,
> >>
> >>Jon
> >>
> >>
> >>
> >>--
> >>To UNSUBSCRIBE, email to debian-knoppix-request@lists.debian.org
> >>with a subject of "unsubscribe". Trouble? Contact
> >>listmaster@lists.debian.org
> >>Archive:
> >>[🔎] 20101025080709.20254q71gx064i68@mail.destar.net">http://lists.debian.org/[🔎] 20101025080709.20254q71gx064i68@mail.destar.net
> >>
> >>
> >>
> >
> >
> >Are syslogd, klogd running?
> >
> >try:
> >
> >ps auxw | grep logd
> >
> >You should see:
> >
> >/sbin/syslogd
> >
> >/sbin/klogd -s
> >
> >Good luck
> >
> >Max
> >--
>
> I'll boot it back up and check but I am trying to see the full dmesg
> log for the system after a boot. I don't think starting those after
> the system has booted will give me what I am looking for. I can
> issue the dmesg command but it is truncated so I don't see the full
> output, I only see however much the buffer size is set for and can't
> figure out a way to increase the size of the buffer.
>
> Jon
Reply to: