Hi James,
SSH Secure Shell daemon behaves as you are describing (dies
after only one connection) when it is running in verbose or
debug mode. The sshd2 daemon does not fork a child process
when running in verbose or debug mode. Verbose and debug
modes should only be used to troubleshoot problems, not for
regular connections. If you have the keyword 'VerboseMode'
set to 'yes' in the /etc/ssh2/sshd2_config file, this is why
your daemon dies after only one connection. Edit your
config file to set 'VerboseMode' to 'no' (without the
quotes), then start the daemon or restart if it is already
running.
As for the startup script, this should be included with the
distribution. If you are installing via rpm, it may not be
installed if you already have a startup script with the same
name present. You may want to rename any existing sshd
scripts prior to rpm installation. If installing via source
code, check in the startup/linux/redhat subdirectory of the
directory where you unpacked the source code. This script
should not requrire any changes to work on SuSe, unless
there have been very recent changes in how SuSe handles
startup scripts.
Hope this helps.
Best Regards,
Steph
--
*********************************
Stephanie Thomas
Technical Support Specialist
SSH Secure Shell
GIAC Certified
Unix Security Administrator
SSH Communications Security Inc.
http://www.ssh.com/support/ssh
*********************************
"James R.Frysinger" wrote:
>
> I am trying to install ssh-3.0.1 on a linux system (SuSE 7.2, kernel
> 2.4) under a university license and am running into some difficulties.
> I compiled (gcc) and installed the package from a downloaded tarball
> with no fatal complaints.
>
> The most significant one occurs after I launch sshd (-->sshd2) manually
> (pending setup of launch-on-boot) in the background. (If I don't do
> this in the background with /usr/local/sbin/sshd2 &) it sits in an
> event loop without returning the system prompt.) Then, it can be
> accessed only once from the outside, then the debugger says the event
> loop is being closed. What can I change in sshd_config to keep the sshd
> daemon alive? I tried "keep alive yes", but that did not work.
>
> The second problem is that SuSE's startup script for ssh is tailored
> for OpenSSH which they provide with their distribution. Does anyone
> have a script I can plagiarize to replace this startup script
> (..../rc3.d/S08sshd) with one for ssh-3.0.1? Likewise for the related
> kill script? If not I suppose I can do surgery, but I'm not experienced
> on editing startup and kill scripts (or any other kind of script for
> that matter). Alternatively, I might try recompiling and installing
> with --with-etcdir=PATH to match the path of the OpenSSH program.
>
> Jim
>
> --
> James R. Frysinger University/College of Charleston
> 10 Captiva Row Dept. of Physics and Astronomy
> Charleston, SC 29407 66 George Street
> 843.225.0805 Charleston, SC 29424
> http://www.cofc.edu/~frysingj [EMAIL PROTECTED]
> Cert. Adv. Metrication Specialist 843.953.7644
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
