Text whizzing by too fast

[utu]

@klauss2008

I've spent a little time with the I/O Redirection reference, for which thanks.
This is a marvelous goldmine of ideas; not mere definitions.
Not a quick read.

[utu]

@klauss2008 re your post #28

You did not get a syntax error, and you got the file established.
I'm cut-and-pasting your exact command, into /etc/init.d/knoppix-startx.
Seems like we should get the same result.

Is yours a live system or normal Debian installed?
I know some here are poor-man installs.

[utu]

@mecho & kl522, in regard to posts #8 & #11

In reviewing this thread, I believe I did not follow-up enough
on your references to the relevancy of /etc/syslog-knoppix.conf.

I've seen what I want in vt #12 in real-time;
I just need a way to capture it for non-real-time study.

Perhaps It is possible to alter this .conf file to get
vt #12 logged to something like /var/log/vt12.log.

This may be a shorter learning curve than trying to tap into
init and/or minirt.gz for some elegant I/O re-direction.

[mecho]

Just comment out the line in /etc/syslog-knoppix.conf and make a new line like this:
# *.*;auth,authpriv.none /dev/tty12
*.*;auth,authpriv.none -/var/log/syslog

This should send the syslog where it supposed to be.

[utu]

@mecho

Outstanding.

Did what you said in post #34 & it works just as I wanted in post #1.

Adding this to my System Tools/Log File Viewer menu collection along with
.xsession-errors.

Thanks a heap.

[utu]

As a postscript.

My syslog now gives a nice current-session-only, scrolllable record of about one minute, 28 seconds
of the boot-up process, which if viewed with Log File Viewer, continues on in real time.

[klaus2008]

@utu re your post #32

My system is not an HD install. I copied the Knoppix directory to my hard disk and use a persistent image.

[utu]

@klaus2008 re post #37

I'm still baffled why I get a syntax error.
I do appreciate all you help.
The references are excellent, but it'll take some time to absorb all that.

[mecho]

Both /tmp and /var/log are mounted using tmpfs, so it really makes no difference at all where syslog is going to be routed to. /var/log only exist in RAM

[utu]

@mecho

So, where do I look for dmesg or kern.log?
I know how to get dmesg from the command line,
but it used to be in /var/log as well.

Why have all the logs been removed, anyway?
I originally thought maybe they'd all been turned-off at one place. You knew better.

Seems like all the XID trash in .xsession-errors, and the db for urlclassifiers amounts
to a lot more Mb than these missing logs.

Also, you are mentioned in another thread about Log File Viewer.
Hope you don't mind.