Starting sshd: /etc/init.d/sshd: line 113: /usr/sbin/sshd: Permission denied
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
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.
Starting sshd: /etc/init.d/sshd: line 113: /usr/sbin/sshd: Permission denied
Hi,
I am running Fedore 8 (x86_64) on Intel Core 2 Duo machine. I have openssh-server.x86_64 version 4.7p1-2.fc8 installed.
When I attempt to start the SSH server as root by using the command '/etc/init.d/sshd start', I get the following message:
===================================================================================
Starting sshd: /etc/init.d/sshd: line 113: /usr/sbin/sshd: Permission denied
[FAILED]
===================================================================================
The line 113 in /etc/init.d/sshd contains: '$SSHD $OPTIONS && success || failure'
I am not being able to find out the problem. Any suggestion?
well dmesg should show you the selinux violation. more often than not it's a case of using tools like chcon to correct selinux context errors rather than changing the underlying policy for selinux, although the latter is still a route to explore if need be.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.