Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
No idea, did you ask google? http://www.google.co.uk/search?q=Pri...does+not+exist
ok, so that looks you just have no dedicated sshd user. but you shouldn't just run sshd itself, you have a formal service script you should be running which may take care of that issue depending on how it handles the service setup.
Last edited by acid_kewpie; 02-22-2008 at 05:56 AM.
it's normally /etc/init.d/sshd you should ideally already be comfortable with tools like ls or even general gui file manager to be able to look in a given directory for a file name in situations like that.
[root@INNOVATE /]$sshd -d
debug3: RNG is ready, skipping seeding
debug2: read_server_config: filename /etc/ssh/sshd_config
debug1: sshd version OpenSSH_3.7.1p2
debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key.
debug1: read PEM private key done: type RSA
debug1: private host key: #0 type 1 RSA
debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key.
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
socket: Address family not supported by protocol
debug1: Bind to port 22 on 0.0.0.0.
Bind to port 22 on 0.0.0.0 failed: Address already in use.
Cannot bind any address.
i've twice said you need to use the proper service scripts. you can't just start sshd in itself and have a healthy system. as you've not heeded that advice you appear to have manaully hacked in an sshd user and all sorts which is really bad system management. use the sysvinit script correctly.
I'm sure they are. did you install ssh yourself from source? if not they will be there. From you're perspective, you're probably best looking for a service control gui tool in your desktop menus, but you probably do have /etc/init.d/sshd to use to gracefully and correctly stop and start services.