Re: SSHD at boot
> Alan, > > Ok, so if /etc/init.d is the standard, why is that the symlink on the newer > systems, rather than the other way around? What kind of things would break > if /etc/init.d was the real directory and the older convention used a > symlink? I don't recall the details, but Red Hat did try what you suggest. I think it was in rawhide. I didn't get caught up in that one, but people did complain about things that didn't work. > > Mark Post > > -Original Message- > From: Alan Cox [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 26, 2002 6:21 PM > To: [EMAIL PROTECTED] > Subject: Re: SSHD at boot > > > > No sure about that, you should read the LSB docs for builds, certainly has > > changed. Right, SuSE did place a symlink there for the RH RPM's But > > calling this "Standard" is a little far, Solaris and system V are > > /etc/init.d But, anybody can make a standard I guess, just have to get > > people to follow it is the trick or be a monopoly like Microsoft and > > change an RFC because you want to put stupid hooks into it for your own > > selfish pleasure, and demand that people use it :~0) > > The standard is /etc/init.d. Which is why RH has a symlink there. Older RH > used /etc/rc.d/init.d and it wouldnt be appropriate to break old third > party apps > -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition.
Re: SSHD at boot
Not necessary, just add the variable "YES" in rc.config for START_SSHD=. This file is located in /etc All lot of options are placed here and the script SuSEconfig builds everything for you. You can also do this through YAST with "System Admin" and then "change configuration file" You need to have the package installed of course. SLES vs the 2.2 kernel seem to differ on that, meaning it looks like ssh is not installed on 2.2 ver. Regards, Jon Jon R. Doyle Sendmail Inc. 6425 Christie Ave Emeryville, Ca. 94608 (o_ (o_ (o_ //\ (/)_ (\)_ V_/_ On Tue, 26 Feb 2002, Rengasamy, Samy wrote: > Create a shell script 'sshd' with the following line > /sbin/sshd or /actual-path-of-ssh-installed/sshd > in directory /etc/rc.d > > Then create a link S10sshd to /etc/rc.d/sshd at directory /etc/rc.d/rc2.d > > Then on reboots, sshd will start running. > > This is specific to SuSe. Red Hat may have a different requirement. > > Thanks, > > Samy Rengasamy. > > -Original Message- > From: Christopher W Gibson [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 26, 2002 1:34 PM > To: [EMAIL PROTECTED] > Subject: SSHD at boot > > > I am trying to start sshd at boot time. Currently I can only start it > manually by: > > ./etc/rc.d/init.d/sshd start > > Where is it normally initialized at boot? > > Thank You, > > Christopher Gibson >
Re: SSHD at boot
Create a shell script 'sshd' with the following line /sbin/sshd or /actual-path-of-ssh-installed/sshd in directory /etc/rc.d Then create a link S10sshd to /etc/rc.d/sshd at directory /etc/rc.d/rc2.d Then on reboots, sshd will start running. This is specific to SuSe. Red Hat may have a different requirement. Thanks, Samy Rengasamy. -Original Message- From: Christopher W Gibson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 26, 2002 1:34 PM To: [EMAIL PROTECTED] Subject: SSHD at boot I am trying to start sshd at boot time. Currently I can only start it manually by: ./etc/rc.d/init.d/sshd start Where is it normally initialized at boot? Thank You, Christopher Gibson
Re: SSHD at boot
> Ok, so if /etc/init.d is the standard, why is that the symlink on the newer > systems, rather than the other way around? What kind of things would break > if /etc/init.d was the real directory and the older convention used a > symlink? Imagine if you have a system running say Red Hat 5.2 and it contains a mix of rpm packages from various vendors and other things like gnu make install built stuff The upgrader would have to move all the existing init.d entries very carefully, handle any in package assumptions and somehow not break anything that wasn't in RPM format. It's simpler the other way around for that reason
Re: SSHD at boot
Alan, Ok, so if /etc/init.d is the standard, why is that the symlink on the newer systems, rather than the other way around? What kind of things would break if /etc/init.d was the real directory and the older convention used a symlink? Mark Post -Original Message- From: Alan Cox [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 26, 2002 6:21 PM To: [EMAIL PROTECTED] Subject: Re: SSHD at boot > No sure about that, you should read the LSB docs for builds, certainly has > changed. Right, SuSE did place a symlink there for the RH RPM's But > calling this "Standard" is a little far, Solaris and system V are > /etc/init.d But, anybody can make a standard I guess, just have to get > people to follow it is the trick or be a monopoly like Microsoft and > change an RFC because you want to put stupid hooks into it for your own > selfish pleasure, and demand that people use it :~0) The standard is /etc/init.d. Which is why RH has a symlink there. Older RH used /etc/rc.d/init.d and it wouldnt be appropriate to break old third party apps
Re: SSHD at boot
> No sure about that, you should read the LSB docs for builds, certainly has > changed. Right, SuSE did place a symlink there for the RH RPM's But > calling this "Standard" is a little far, Solaris and system V are > /etc/init.d But, anybody can make a standard I guess, just have to get > people to follow it is the trick or be a monopoly like Microsoft and > change an RFC because you want to put stupid hooks into it for your own > selfish pleasure, and demand that people use it :~0) The standard is /etc/init.d. Which is why RH has a symlink there. Older RH used /etc/rc.d/init.d and it wouldnt be appropriate to break old third party apps
Re: SSHD at boot
No sure about that, you should read the LSB docs for builds, certainly has changed. Right, SuSE did place a symlink there for the RH RPM's But calling this "Standard" is a little far, Solaris and system V are /etc/init.d But, anybody can make a standard I guess, just have to get people to follow it is the trick or be a monopoly like Microsoft and change an RFC because you want to put stupid hooks into it for your own selfish pleasure, and demand that people use it :~0) Regards, Jon Jon R. Doyle Sendmail Inc. 6425 Christie Ave Emeryville, Ca. 94608 (o_ (o_ (o_ //\ (/)_ (\)_ V_/_ On Tue, 26 Feb 2002, Rick Troth wrote: > On Tue, 26 Feb 2002, Jon R. Doyle wrote: > > > /etc/rc.d/init.d ? Oh, right that is the runlevels on RH. Solaris, SuSE > > blah blah use /etc/init.d think that is system 5 or LSB some such > > standard, not sure why RH adds the other layer. > > /etc/rc.d/init.d should be (as in "if it is not, then make it so") > a sym-link to /etc/init.d, iff your distro or system uses the latter. > > That is, the standard place people and packages look to find > INIT scripts is /etc/rc.d/init.d. Build for, and train for, > widest operability and least astonishment. >
Re: SSHD at boot
On Tue, 26 Feb 2002, Jon R. Doyle wrote: > /etc/rc.d/init.d ? Oh, right that is the runlevels on RH. Solaris, SuSE > blah blah use /etc/init.d think that is system 5 or LSB some such > standard, not sure why RH adds the other layer. /etc/rc.d/init.d should be (as in "if it is not, then make it so") a sym-link to /etc/init.d, iff your distro or system uses the latter. That is, the standard place people and packages look to find INIT scripts is /etc/rc.d/init.d. Build for, and train for, widest operability and least astonishment.
Re: SSHD at boot
> Where is it normally initialized at boot? This is standard "SysV INIT" stuff. Is it SuSE or RedHat? No great difference, except that they prefer different run levels. I'll use SuSE's run levels for this example. Say the default run level is 3. /etc/rc.d/rc3.d contains sym-links to scripts which physically reside in /etc/rc.d/init.d. SuSE may also set the default run-level to 2, for which the "startup folder" is /etc/rc.d/rc2.d. The links should look something like /etc/rc.d/rc3.d/S90sshd -> /etc/rc.d/init.d/sshd /etc/rc.d/rc3.d/K10sshd -> /etc/rc.d/init.d/sshd These may also be in your rc2.d directory (on SuSE) allowing that SSHD will start in both run-levels, 2 and 3. Or it might be in just one of them. (It's a sysadmin choice.) The effect is that INIT scans the directory matching the run-level and executes all the "S" scripts, in sequence, with a "start" parm when entering the run level. When leaving a run-level, it executes all the "K" scripts, supplying each with a "stop" parm.
Re: SSHD at boot
Humm, right, I think the LSB thing might be where this came in, seems I remember that RH on or around 7.2 started supporting LSB too, I thnk I saw them talk about this or it was the LSB folks in NY last month at LWE. Regards, Jon On 2/26/02 1:45 PM, "John Summerfield" <[EMAIL PROTECTED]> wrote: >> On SuSE this is placed into /etc/init.d/rc.config as START_SSHD=YES >> >> /etc/rc.d/init.d ? Oh, right that is the runlevels on RH. Solaris, SuSE >> blah blah use /etc/init.d think that is system 5 or LSB some such >> standard, not sure why RH adds the other layer. > > > So far as you're concerned, RH uses /etc/init.d too. It used to use the other, > but changed before S/390. There's a bit of symlinkery in some circumstances > for compatibility with things that understand the old way better. > > > > -- > Cheers > John Summerfield > > Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ > > Note: mail delivered to me is deemed to be intended for me, for my > disposition. >
Re: SSHD at boot
> On SuSE this is placed into /etc/init.d/rc.config as START_SSHD=YES > > /etc/rc.d/init.d ? Oh, right that is the runlevels on RH. Solaris, SuSE > blah blah use /etc/init.d think that is system 5 or LSB some such > standard, not sure why RH adds the other layer. So far as you're concerned, RH uses /etc/init.d too. It used to use the other, but changed before S/390. There's a bit of symlinkery in some circumstances for compatibility with things that understand the old way better. -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition.
Re: SSHD at boot
I'm loving chkconfig...so much easier...although it is still nice to know how chkconfig works... I learn something new everyday from you folks. Thanks! and yeah, in most cases I'd agree that you want to check with what the vendor recommends. I have certain reasons I want sshd running in those specific runlevels. Paul >>> [EMAIL PROTECTED] 02/26/02 03:58PM >>> I recommend you do it My Way (TM Frankie). Check the script header for runlevels the vendor thinks it should be run in. If you change that, rerun chkconfig. > -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition.
Re: SSHD at boot
On SuSE this is placed into /etc/init.d/rc.config as START_SSHD=YES /etc/rc.d/init.d ? Oh, right that is the runlevels on RH. Solaris, SuSE blah blah use /etc/init.d think that is system 5 or LSB some such standard, not sure why RH adds the other layer. Regards, Jon Jon R. Doyle Sendmail Inc. 6425 Christie Ave Emeryville, Ca. 94608 (o_ (o_ (o_ //\ (/)_ (\)_ V_/_ On Wed, 27 Feb 2002, John Summerfield wrote: > > I am trying to start sshd at boot time. Currently I can only start it > > manually by: > > > > ./etc/rc.d/init.d/sshd start > > > > Where is it normally initialized at boot? > > Red Hat? > chkconfig --list > chkconfig sshd on > man chkconfig > > -- > Cheers > John Summerfield > > Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ > > Note: mail delivered to me is deemed to be intended for me, for my > disposition. >
Re: SSHD at boot
> > I am trying to start sshd at boot time. Currently I can only start it > > manually by: > > > > ./etc/rc.d/init.d/sshd start > > > > Where is it normally initialized at boot? > > chkconfig --level 345 sshd on > > Or via the gui tools, I guess the command line is the preferred S/390 beast > though ? If you don't like the CLI, take a look at webmin. -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition.
Re: SSHD at boot
> I am trying to start sshd at boot time. Currently I can only start it > manually by: > > ./etc/rc.d/init.d/sshd start > > Where is it normally initialized at boot? Red Hat? chkconfig --list chkconfig sshd on man chkconfig -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition.
Re: SSHD at boot
> All depends on what run level you want SSHD running at. Mine > is running at rc2.d and rc3.d. Just symlink from there into the > init directory like this: > > cd /etc/rc.d/rc2.d/ > ln -s ../init.d/sshd Sxxsshd > cd /etc/rc.d/rc3.d/ > ln -s ../init.d/sshd Sxxsshd I recommend you do it My Way (TM Frankie). Check the script header for runlevels the vendor thinks it should be run in. If you change that, rerun chkconfig. > -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition.
Re: SSHD at boot
> I am trying to start sshd at boot time. Currently I can only start it > manually by: > > ./etc/rc.d/init.d/sshd start > > Where is it normally initialized at boot? chkconfig --level 345 sshd on Or via the gui tools, I guess the command line is the preferred S/390 beast though ?
Re: SSHD at boot
Quoting "Paul C. Williamson" <[EMAIL PROTECTED]>: > cd /etc/rc.d/rc2.d/ > ln -s ../init.d/sshd Sxxsshd > cd /etc/rc.d/rc3.d/ > ln -s ../init.d/sshd Sxxsshd Or you can use 'chkconfig' for redhat and 'rctab' for suse. It will do the work for you. :-) Yuval. - This mail sent through IMP: http://horde.org/imp/
Re: SSHD at boot
All depends on what run level you want SSHD running at. Mine is running at rc2.d and rc3.d. Just symlink from there into the init directory like this: cd /etc/rc.d/rc2.d/ ln -s ../init.d/sshd Sxxsshd cd /etc/rc.d/rc3.d/ ln -s ../init.d/sshd Sxxsshd where "xx" is what position you want it to start. Mine start in position 94 (fairly late in the boot game). The directory may be /etc/rc2.d and /etc/rc3.d, it depends on what version/flavor of os you are running. Paul >>> [EMAIL PROTECTED] 02/26/02 02:33PM >>> I am trying to start sshd at boot time. Currently I can only start it manually by: ./etc/rc.d/init.d/sshd start Where is it normally initialized at boot? Thank You, Christopher Gibson
Re: SSHD at boot
For the RH releases, you'll find them in the /etc/rc.x (where x = runlevel) directories. For example, my runlevel 3 sshd start script is /etc/rc.3/S55sshd. --Jim-- James S. Tison Senior Software Engineer TPF Laboratory / Architecture IBM Corporation +1 203 486-2835 (voice/fax) [EMAIL PROTECTED] Christopher W Gibson/Dallas/ContTo: [EMAIL PROTECTED] r/IBM@IBMUS cc: Sent by: Linux on Subject: SSHD at boot 390 Port <[EMAIL PROTECTED] ST.EDU> 02/26/2002 14:33 Please respond to Linux on 390 Port I am trying to start sshd at boot time. Currently I can only start it manually by: ./etc/rc.d/init.d/sshd start Where is it normally initialized at boot? Thank You, Christopher Gibson
SSHD at boot
I am trying to start sshd at boot time. Currently I can only start it manually by: ./etc/rc.d/init.d/sshd start Where is it normally initialized at boot? Thank You, Christopher Gibson
