Slackware This Forum is for the discussion of Slackware 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
04-13-2006, 12:26 PM
|
#1
|
Member
Registered: Aug 2005
Distribution: Slackware, Fedora, CentOS
Posts: 42
Rep:
|
Trying to link logs to TTY12
Here's my issue.
I would like to be able to switch over to tty12 and see the system activity logs scrolling down the page. Problem is, I don't know where to start!
If you've done it before, I would appreciate any advice you might have. Thank you!
|
|
|
04-13-2006, 12:34 PM
|
#2
|
LQ Veteran
Registered: Sep 2003
Posts: 10,532
|
Hi,
You need to add/change a line in your /etc/syslog.conf
kern.warn;*.err /dev/tty12
This will print kernel warnings (and more severe) and all errors (and more severe) to /dev/tty12 You can change what you want to print by changing facility and level.
man syslog.conf for details.
You do need to restart syslogd after changing /etc/syslog.conf
Hope this helps.
|
|
|
04-13-2006, 02:32 PM
|
#3
|
Member
Registered: Aug 2005
Distribution: Slackware, Fedora, CentOS
Posts: 42
Original Poster
Rep:
|
Quote:
Originally Posted by druuna
Hi,
You need to add/change a line in your /etc/syslog.conf
kern.warn;*.err /dev/tty12
This will print kernel warnings (and more severe) and all errors (and more severe) to /dev/tty12 You can change what you want to print by changing facility and level.
man syslog.conf for details.
You do need to restart syslogd after changing /etc/syslog.conf
Hope this helps.
|
It helps a great deal! Thank you very much Druuna! I'm actually going to use this on my bosses' new Slack desktop. Now for the office server, is it possible to have all information go to tty12? Like all the apache logs, FreeRadius, clamav and such?
|
|
|
04-13-2006, 02:50 PM
|
#4
|
LQ Veteran
Registered: Sep 2003
Posts: 10,532
|
Hi again,
Not all programs use syslogd for the output generated. Some do have that possibility, but the default is otherwise, others 'only' have their own log facility.
I know apache can use syslogd (at least 2.0 can), don't know if the others you mention can. Take a look at the documentation, man pages and the net.
Do watch out that you don't log everything to a tty, it could case slowness. Something like *.* /dev/tty12 would be overkill. All, including debug(!!), messages generated will be send to tty12.
Hope this helps.
|
|
|
All times are GMT -5. The time now is 10:35 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|