MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
see the log files in /var
If logging is not enabled, do that
Thanks Amani,
How do I enable boot logging (Mandriva 2008)? I can find an empty file /var/log/boot.log and an entry local7.* -> pointing to that file in /etc/syslog.conf, but no explanation on how to do. WWW does'nt help.
regards
torben friis
Hi repo,
I had to make the file, but it had no effect. Could it be, since extensive searching www gives no result, that it is not possible to log to boot.log?
regards
torben friis
I use Mandriva 2009.0 here and boot logging is enabled by default in /etc/sysconfig
The boot log file(s) are located at /var/log/boot.log and (at present) four archived log files exist: /var/log/boot.log.1.gz thru /var/log/boot.log.4.gz.
bootlogd is included in the package sysvinit-2.86-8mdv2009.0.x86_64 (on my system). There is also a 32 bit package sysvinit-2.86-8mdv2009.0.i586
I use Mandriva 2009.0 here and boot logging is enabled by default in /etc/sysconfig
The boot log file(s) are located at /var/log/boot.log and (at present) four archived log files exist: /var/log/boot.log.1.gz thru /var/log/boot.log.4.gz.
bootlogd is included in the package sysvinit-2.86-8mdv2009.0.x86_64 (on my system). There is also a 32 bit package sysvinit-2.86-8mdv2009.0.i586
HTH,
Thanks repo and ernie,
I found /sbin/bootlogd and ran it and got the message: cannot find console device &"-:1 in /dev.
But I have to install it so it runs when I boot - right?
I have Mandriva 2008 (32 bit), free and there is only /var/log/boot.log
regards
torben
Hi, to see what your kernel output during boot, type
dmesg |more
To check the errors when x starts, open as text
/home/user-name/.xsession-errors
Cheers, Glenn
<edit>You might need root access to view the log files in /var/log/, depends on security setting (I think).</edit>
Hi Glenn,
I did not understand .xsession-errors. I now get just one line in boot.log for every boot telling that resolv.conf has been updated.
But if I key Esc and I at a certain point in boot I can step through the boot. Maybe the best.
regards
torben
From a shell, or a teminal for the shell from your favourite window manager,
like xterm or konsole.
For long texts you may need to increase the buffer for
konsole to be able to display all the lines, not just the
last bit.
This is how you view the messages captured during (AFTER) boot.
dmesg | more
use the "space" key to scroll down as you read. When it reaches the end it exits.
You can copy and paste from the terminal/shell if you have a GUI. For later reference.
To view the screen errors, if any, type
cat /var/log/Xorg.0.log | grep EE
This will only display lines with EE from the current log.
To view the whole .xsession-errors (it's a hidden-system file)file, type
vim ~/.xsession-errors
use the vi manual to get the key strokes for vi...
Code:
arrows and PageUp PageDown work as normal to navigate
i insert, to insert
esc to exit (all modes) insert mode
:wq to write and quit
:q to quit without writing
! to force command :wq
dd delete line
dw delete word
a enter append mode
e enter edit mode
/ find forwards
:w save
see how you go, Glenn
Last edited by GlennsPref; 12-02-2008 at 07:36 PM.
From a shell, or a teminal for the shell from your favourite window manager,
like xterm or konsole.
For long texts you may need to increase the buffer for
konsole to be able to display all the lines, not just the
last bit.
This is how you view the messages captured during (AFTER) boot.
dmesg | more
use the "space" key to scroll down as you read. When it reaches the end it exits.
You can copy and paste from the terminal/shell if you have a GUI. For later reference.
To view the screen errors, if any, type
cat /var/log/Xorg.0.log | grep EE
This will only display lines with EE from the current log.
To view the whole .xsession-errors (it's a hidden-system file)file, type
vim ~/.xsession-errors
use the vi manual to get the key strokes for vi...
Code:
arrows and PageUp PageDown work as normal to navigate
i insert, to insert
esc to exit (all modes) insert mode
:wq to write and quit
:q to quit without writing
! to force command :wq
dd delete line
dw delete word
a enter append mode
e enter edit mode
/ find forwards
:w save
see how you go, Glenn
Hi Glenn,
Thanks very much. That was clear.
best regards
torben
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
