Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Why is jlightner's answer useless?? You could at least tell us (the persons willing to help) why a particular answer is useless or helpful.
Besides that: jlightner has a very valid point. I've used suse up to version 8 and messages were logged in /var/log, not var/adm.
- did you change the location yourself?
- did you check /etc/syslog.conf to check the actual log locations and rules?
- did you check the startup file?
- did you find out why the syslog daemon wasn't running in the first place?
Having been to India I'm surprised to find someone as rude as you claiming to be from there. Most Indians I met were very polite. In future you might thank the poster for his input then attempt to reclarify your question or at the very least just ignore the post at all. I'll forego bothering to add my "useless" input on any future posts I see by you.
================================================================================== /etc # more syslog.conf
# Tivoli logfile adapter entry, ID=
# End of logfile adapter entry, ID=
stp05508:/etc # more syslog.conf.FUSE.1134011953
# /etc/syslog.conf - Configuration file for syslogd(8)
# For info about the format of this file, see "man syslog.conf".
# print most on tty10 and on the xconsole pipe
# enable this, if you want that root is informed
# immediately, e.g. of logins
# all email-messages in one file
# all news-messages
# these files are rotated and examined by "news.daily"
# enable this, if you want to keep all news messages
# in one file
# Warnings in one file
# save the rest in one file
# enable this, if you want to keep all messages
# in one file