Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
This is suse 9.0 pro .... w/YOU updates
generic install .... all default.
We have a problem where sshd vanishes in the night. It works when rebooted, but over a day or two the sshd daemon goes away. This is a new (temporary) install for a class with 10-15 people accessing from outside our LAN. The students have an unknown mix of OS/clients. They are using ssh/sftp. All we know is we get a call from someone not able to connect and, sure enough, the daemon is gone. We restart the server ... repeat process.
My question is about capturing exactly when the daemon fails. The messages file (as it defaults) shows nothing of interest .... just pre-failure connections.
I'm looking for suggestions as to if and where messages would/could be generated by the failing daemon.
Would a syslog.conf entry along the lines of "auth.debug /var/log/autherr" possibly capture the act of failing? .... as opposed to only reflecting a deliberate event ...(student connecting, etc)? If I kill it manually there's an entry ... but I'm issuing a local shell command.
Is syslog the way to go here? .... all suggestions welcome.