Solaris / OpenSolarisThis forum is for the discussion of Solaris and OpenSolaris.
General Sun, SunOS and Sparc related questions also go here.
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.
Just recently i've applied my first patch cluster on a Solaris 9 server. The patch was pretty uneventfull; however, now when i reboot the system SSHD is not running. I have the startup script in the /etc/rc3.d/ folder and indeed when i login to the system i see that i am in run-level 3. The script /etc/init.d/sshd matches the one found in the rc3.d folder, but for some reason it does not start up sshd. I can go into the /etc/rc3.d folder and startup sshd using the script manually just fine.
As an update. I noted that after the system booted i have an error message saying that sshd service was unable to bind on port 22 on IP address ::. When i look in the sshd_config file i see that the listening ip address was set to "::". I understand this means "bind to any available ip for either IPv4 or IPv6". We do not use IPv6 on our network, so i simply changed it to 0.0.0.0 so it binds to any IPv4 address. Now it works fine.
Any thoughts as to why the "any" distinction for IPv6 is giving me trouble, where as the IPv4 "any" distinction isn't?
I've got the problem solved, but any further help/ideas on the IPv6 versus IPv4 would be cool. Thanks again jll for the response!
When i look through the logs, i see a message about copying the old sshd bin to sshd.113273-11, but i do not see any similar preservation techniques used for the sshd_config file.
Also immediately after appling the patch, i looked at my sshd_config and noted that it was not overwritten as my previous settings where still in the file. The sshd_config file is dated 01/10/08 (european time format) on the inside.
So the file was not overwritten and we have always had the IPv6 and IPv4 binding of "ListenAddress ::"