SLES7 (Suse 7.2) and runlevel
Hello! I have "strange" ;-) (for me) problem. I have several self written scripts in /etc/rc.d I linked them with ln to appropriate runlevel as I usually do on RH ( I don't like chkconfig). But I found that yast2 renames my link names from S20... to S00 or S01... How can I tell to yast to not do this? Thank you!
On Tue, Aug 27, 2002 at 08:36:38AM +0500, Dmitry Melekhov wrote:
Hello!
I have "strange" ;-) (for me) problem. I have several self written scripts in /etc/rc.d
/etc/init.d seems to be a more appropriate location
I linked them with ln to appropriate runlevel as I usually do on RH ( I don't like chkconfig).
If you provide specially formatted comments at the beginning of your script the numbers in symbolic links can be calculated automatically for you. Please see man page of insserv(8).
But I found that yast2 renames my link names from S20... to S00 or S01... How can I tell to yast to not do this?
Please read man page init.d(7). It explains pretty much the concept. If you prefer to make all changes manually, change ENABLE_SUSECONFIG to "no" Regards, -Kastus
----- Original Message ----- From: "Konstantin (Kastus) Shchuka" <kastus@tsoft.com> To: <suse-linux-e@suse.com> Sent: Tuesday, August 27, 2002 9:08 AM Subject: Re: [SLE] SLES7 (Suse 7.2) and runlevel
On Tue, Aug 27, 2002 at 08:36:38AM +0500, Dmitry Melekhov wrote:
Hello!
I have "strange" ;-) (for me) problem. I have several self written scripts in /etc/rc.d
/etc/init.d seems to be a more appropriate location
I linked them with ln to appropriate runlevel as I usually do on RH ( I don't like chkconfig).
If you provide specially formatted comments at the beginning of your
Shure, sorry, I wrote like about RH 6.2 ;-) script
the numbers in symbolic links can be calculated automatically for you. Please see man page of insserv(8).
I readed it and can not find how to set start or stop number, I mean XX in SXX or KXX.
But I found that yast2 renames my link names from S20... to S00 or S01... How can I tell to yast to not do this?
Please read man page init.d(7). It explains pretty much the concept.
If you prefer to make all changes manually, change ENABLE_SUSECONFIG to "no"
This is not what I want, I only want SuSEconfig doesn't change my init scripts order :-)
On Tue, Aug 27, 2002 at 10:20:39AM +0400, Dmitry Melekhov wrote:
Please see man page of insserv(8).
I readed it and can not find how to set start or stop number, I mean XX in SXX or KXX.
It is not possible to set up exact number. insserv caclulates the number automatically on the basis of dependency information provided in the script. And actually, this is all that is needed. All you care is that your script is not started *before* some other script or it should run *before* something else is run. It is much easier to maintain.
But I found that yast2 renames my link names from S20... to S00 or S01... How can I tell to yast to not do this?
Please read man page init.d(7). It explains pretty much the concept.
If you prefer to make all changes manually, change ENABLE_SUSECONFIG to "no"
This is not what I want, I only want SuSEconfig doesn't change my init scripts order :-)
This is not the way SuSE is designed. Sorry. SuSE is for *lazy* sysadmins who do not calculate the numbers in symlinks ;-) Regards, -Kastus
Konstantin (Kastus) Shchuka wrote:
On Tue, Aug 27, 2002 at 10:20:39AM +0400, Dmitry Melekhov wrote:
Please see man page of insserv(8).
I readed it and can not find how to set start or stop number, I mean XX in SXX or KXX.
It is not possible to set up exact number. insserv caclulates the number automatically on the basis of dependency information provided in the script.
And actually, this is all that is needed. All you care is that your script is not started *before* some other script or it should run *before* something else is run. It is much easier to maintain.
Thank you, I understand... [skip]
This is not what I want, I only want SuSEconfig doesn't change my init scripts order :-)
This is not the way SuSE is designed. Sorry. SuSE is for *lazy* sysadmins who do not calculate the numbers in symlinks ;-)
Sort of AI like in MS products? ;-) OK, I don't like it, but I can't change this :-(
Konstantin (Kastus) Shchuka wrote:
On Tue, Aug 27, 2002 at 10:20:39AM +0400, Dmitry Melekhov wrote:
Please see man page of insserv(8).
I readed it and can not find how to set start or stop number, I mean XX in SXX or KXX.
It is not possible to set up exact number. insserv caclulates the number automatically on the basis of dependency information provided in the
And actually, this is all that is needed. All you care is that your
btw, I hope there is Suse's guys here? IMHO, would be better to nit try to change link for servers which has no desciption- this will allow manual and automatic ways coexist :-) script. script
is not started *before* some other script or it should run *before* something else is run. It is much easier to maintain.
Thank you, I understand...
[skip]
This is not what I want, I only want SuSEconfig doesn't change my init scripts order :-)
This is not the way SuSE is designed. Sorry. SuSE is for *lazy* sysadmins who do not calculate the numbers in symlinks ;-)
Sort of AI like in MS products? ;-) OK, I don't like it, but I can't change this :-(
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Dmitry Melekhov wrote:
btw, I hope there is Suse's guys here? IMHO, would be better to nit try to change link for servers which has no desciption- this will allow manual and automatic ways coexist :-)
I asked our developers, see below. Michael ===========================================================
Yes, this definitely is true and exactly *because* the info for insserv is missing. That's why you *have* to provide that info and it's also why we provide /etc/init.d/skeleton as a template for self written init scripts.
IOW, if he just adds the INIT INFO header, which won't harm on other distributions, he will be fine. Other 3rd party vendors do that, too. Please point him to the fact that this is the LSB conform way of doing it, cf. http://www.linuxbase.org/spec/refspecs/LSB_1.2.0/gLSB/initscrcomconv.html In fact, he can (and should) call /usr/lib/lsb/install_initd to install his script (which calls insserv, if he likes it or not) Peter
----- Original Message ----- From: "Michael Hasenstein" <mha@suse.com> To: "Dmitry Melekhov" <dm@belkam.com> Cc: <suse-linux-e@suse.com> Sent: Tuesday, August 27, 2002 7:27 PM Subject: Re: [SLE] SLES7 (Suse 7.2) and runlevel
Dmitry Melekhov wrote:
btw, I hope there is Suse's guys here? IMHO, would be better to nit try to change link for servers which has no desciption- this will allow manual and automatic ways coexist :-)
I asked our developers, see below.
Michael
[skip]
Please point him to the fact that this is the LSB conform way of doing it, cf. http://www.linuxbase.org/spec/refspecs/LSB_1.2.0/gLSB/initscrcomconv.html
OK. If this is standard and I can't resist. I don't like it , but .... ;-) And I want to quote standard: <quote> The comment conventions described in this session are only required for use by LSB-compliant applications; system init scripts as provided by LSB-compliant run-time environments are not required to use the scheme outlined here. </quote> Current behavoir makes Suse incompatible with such applications, for instance, for targeted to RH. Thank you!
On Tue, Aug 27, 2002 at 10:55:50AM +0500, Dmitry Melekhov wrote:
This is not what I want, I only want SuSEconfig doesn't change my init scripts order :-) This is not the way SuSE is designed. Sorry. SuSE is for *lazy* sysadmins who do not calculate the numbers in symlinks ;-) Sort of AI like in MS products? ;-)
It has nothing to do neither with AI nor MS. It's kind of safety feature. E.g. You can't start sshd while network is down. When you add more scripts, the numbering just shifts to allow room for new scripts.
OK, I don't like it, but I can't change this :-(
In any case, your scripts depend on other daemons to be running before they can start. Just put this dependency info into your scripts and install them with insserv. Otherwise, it's about choice. There are many other distros around. Regards, -Kastus
Konstantin (Kastus) Shchuka wrote:
On Tue, Aug 27, 2002 at 10:55:50AM +0500, Dmitry Melekhov wrote:
This is not what I want, I only want SuSEconfig doesn't change my init scripts order :-)
This is not the way SuSE is designed. Sorry. SuSE is for *lazy* sysadmins who do not calculate the numbers in symlinks ;-)
Sort of AI like in MS products? ;-)
It has nothing to do neither with AI nor MS. It's kind of safety feature. E.g. You can't start sshd while network is down. When you add more scripts, the numbering just shifts to allow room for new scripts.
:-) As I wrote I think that there is no description in script yast (or insserv) should not change symlinks to it. Current behavior is wrong, imho. Other aspects are strange for me, but they are acceptable ;-)
OK, I don't like it, but I can't change this :-(
In any case, your scripts depend on other daemons to be running before they can start. Just put this dependency info into your scripts and install them with insserv.
Yes, I did this. This is why I asked for help :-)
Otherwise, it's about choice. There are many other distros around.
I prefer RedHat. But I have to run Suse -I run SLES7 for SAP R/3- this was only choise for R/3 for long time... :-(
participants (3)
-
Dmitry Melekhov -
Konstantin (Kastus) Shchuka -
Michael Hasenstein