|
Bugzilla – Full Text Bug Listing |
| Summary: | sshd Restart Failure | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Gregory Taylor <gtaylor> |
| Component: | Network | Assignee: | Andreas Schwab <schwab> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | postadal |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
IMHO no /sbin nor /usr/sbin in path after su Use su -. |
I get the following error when trying to restart the sshd on SuSe 10.0 beta 1: linux:/etc/init.d # ./sshd restart Shutting down SSH daemon./sshd: line 74: killproc: command not found failed Starting SSH daemon./sshd: line 64: startproc: command not found failed Editing the file, I was able to remedy the problem by pointing to /sbin/killproc and /sbin/startproc rather than just referring to killproc and startproc as if they were in my path. So depending on how you want to fix this, a path entry can be added or an absolute path can be used. I'd almost suggest going with the absolute path since their locations are going to be constant and it'd avoid problems caused by people kludging with their $PATH variables.