[SLE] YaST, rc.config and startup scripts
Greetings, I need to set ssh up to run full-time on my system, and start at boot. So far I've read the man pages for init.d, edited the skeleton file for sshd, and got all the ssh files in the correct places, other than the links in the rc.d directories. Now I just need a little help tying it altogether, mainly with the rc.config file. There isn't already a line in my rc.config to START_SSHD, and I'm wondering if I can just add that in myself manually or through YaST. I didn't see how in YaST to add something that isn't already present. So, can I just edit the rc.config with START_SSHD, then run SuSEconfig and be ok or am I missing something somewhere? Thanks for any help/advice Rob Wright robwright@ponacacity.net -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Rob Wright wrote:
Greetings,
I need to set ssh up to run full-time on my system, and start at boot. So far I've read the man pages for init.d, edited the skeleton file for sshd, and got all the ssh files in the correct places, other than the links in the rc.d directories. Now I just need a little help tying it altogether, mainly with the rc.config file. There isn't already a line in my rc.config to START_SSHD, and I'm wondering if I can just add that in myself manually or through YaST. I didn't see how in YaST to add something that isn't already present. So, can I just edit the rc.config with START_SSHD, then run SuSEconfig and be ok or am I missing something somewhere?
Thanks for any help/advice
Rob Wright robwright@ponacacity.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Dear Rob, If you instal ssh as a rpm than you will have the open to start sshd at boot time. If you installed your own version you can either make your own script. Or use the start scripts that come with ssh.rpm . To do this first install the rpm package and than install ssh in the same location. This is a quit dirty solution. An other solution is to install the source rpm and adapt this to the new ssh version. Regards, Joop. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I realise many of you will not be happy with SSH2 licensing arrangements, but for those who need / want it (please note this isn't an ad., I'm just an ordinary punter): I dropped a line to the list concerning trying to build SSH 2.0.13 a while ago, and despite getting some kind help could not install it either from the source or the rpms. Others may have had similar problems. There is now a new release at www.ssh.com , numbered 2.2.0, and after downloading the tarball for this I was able to install it without difficulty using the recommended ./configure, make, make install. You do need to make sure you kill the 'old' sshd and manually start sshd2 before it will work. There is a script sshd2.startup in the tar archive, and if this is put into rc.d and the symlinks adjusted sshd2 will start automatically on boot. The ssh1 compatibility appears, on my limited testing, to work better than before, but you have to have had ssh1 set up on your computer previously for this to work. If you want to go from no ssh at all to a working ssh1 & 2, you need to download and install ssh1, then follow that by installing ssh2. There is also a 2.2.0 version of the windows client free for non-commercial use, and this seems to work quite nicely too. It includes a version of scp for windows, but I haven't played with that. Cheers all, Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB UK Tel: +44 (0)161 834 7961 Fax: +44 (0)161 839 5797 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
I realise many of you will not be happy with SSH2 licensing arrangements, but for those who need / want it (please note this isn't an ad., I'm just an ordinary punter):
I dropped a line to the list concerning trying to build SSH 2.0.13 a while ago, and despite getting some kind help could not install it either from
the
source or the rpms. Others may have had similar problems.
There is now a new release at www.ssh.com , numbered 2.2.0, and after downloading the tarball for this I was able to install it without difficulty using the recommended ./configure, make, make install. You do need to make sure you kill the 'old' sshd and manually start sshd2 before it will work. There is a script sshd2.startup in the tar archive, and if this is put into rc.d and the symlinks adjusted sshd2 will start automatically on boot. The ssh1 compatibility appears, on my limited testing, to work better than before, but you have to have had ssh1 set up on your computer previously for this to work. If you want to go from no ssh at all to a working ssh1 & 2, you need to download and install ssh1, then follow that by installing ssh2.
There is also a 2.2.0 version of the windows client free for non-commercial use, and this seems to work quite nicely too. It includes a version of scp for windows, but I haven't played with that.
Cheers all, Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB UK
Tel: +44 (0)161 834 7961 Fax: +44 (0)161 839 5797
You might also want to check out http://www.openssh.com (OpenSSH from the OpenBSD project), it is a really nice program and the licensing term people could argue are a little less stirct and is freely avaiable, even for commerical usage. It has recently added support for the SSH2 protocol amoung other feartures (like scp, port/X11 forwarding, etc). -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Hi, On Thu, Jun 29 2000 at 13:29 -0500, Rob Wright wrote:
I need to set ssh up to run full-time on my system, and start at boot. So far I've read the man pages for init.d, edited the skeleton file for sshd, and got all the ssh files in the correct places, other than the links in the rc.d directories. Now I just need a little help tying it altogether, mainly with the rc.config file. There isn't already a line in my rc.config to START_SSHD, and I'm wondering if I can just add that in myself manually or through YaST. I didn't see how in YaST to add something that isn't already present. So, can I just edit the rc.config with START_SSHD, then run SuSEconfig and be ok or am I missing something somewhere?
You can add it manually. Make sure your /sbin/init.d/sshd script does evaluate it: --------------------------------------------------------> . /etc/rc.config # Determine the base and follow a runlevel link name. base=${0##*/} link=${base#*[SK][0-9][0-9]} # Force execution if not called by a runlevel directory. test $link = $base && START_SSHD=yes test "$START_SSHD" = yes || exit 0 <-------------------------------------------------------- Btw. you don't have to run SuSEconfig in this case. Ciao, Stefan -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Thanks to everyone who replied! I got the information that I needed and have it all in place. Rob Wright robwright@poncacity.net On Thu, 29 Jun 2000, you wrote:
Greetings,
I need to set ssh up to run full-time on my system, and start at boot. So far I've read the man pages for init.d, edited the skeleton file for sshd, and got all the ssh files in the correct places, other than the links in the rc.d directories. Now I just need a little help tying it altogether, mainly with the rc.config file. There isn't already a line in my rc.config to START_SSHD, and I'm wondering if I can just add that in myself manually or through YaST. I didn't see how in YaST to add something that isn't already present. So, can I just edit the rc.config with START_SSHD, then run SuSEconfig and be ok or am I missing something somewhere?
Thanks for any help/advice
Rob Wright robwright@ponacacity.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Hi rob, I think it will be to everyone's benefit if you share the info, right? Nadeem Rob Wright wrote:
Thanks to everyone who replied! I got the information that I needed and have it all in place.
Rob Wright robwright@poncacity.net
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (6)
-
fwilde＠chethams.org.uk -
jbarnett＠axil.netmate.com -
jboonen＠worldonline.nl -
nhasan＠usa.net -
robwright＠poncacity.net -
stefan.troeger＠wirtschaft.tu-chemnitz.de