Hi Carlos, The uninstall script that uses "insserv -r " is able to remove all symbolic links from all runlevels. But the entries from depend.start and depend.stop are not getting deleted !! I am not sure if I discovered a bug. But I will report to the bugzilla team, who can verify the same with another r application/scenario. Thanks for all (especially Philipp) your help in this issue and the "Automatic restart of services" issue. Regards, Murali. -----Original Message----- From: Carlos E. R. [mailto:robin.listas@telefonica.net] Sent: Thursday, June 12, 2008 7:50 PM To: OS-en Subject: Re: [opensuse] clean uninstall -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-06-12 at 09:21 -0400, Kamal, Murali wrote:

Hi all,

I created the LSB header in my service_start scripts and used another Post_install script to execute the commands "insserv " to get them into various runlevels and boot scripts during installation process.

I used post_uninstall script which contains "insserv -r " which removes symbolic links from all runlevels during uninstallation.

Now when I uninstall my application, it is not clean, which means, my service names remain in /etc/init.d/.depend.start and .depend.stop files. what should I do to remove the entries from different locations ?

I think you may have discovered a bug. You could also try, manually: chkconfig yourservice chkconfig yourservice on chkconfig yourservice off and check the depends files and the links. If the links dissapear, but not the entries in the depend files, then (IMO) you discovered a bug, which you could report to Bugzilla. If neither links and entries dissapear, there must be something incorrect in your LSB header. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIUTCztTMYHG2NR9URAnGyAJsEgwoWnkOetcPhKTROm3xo4kIL/ACdEJKZ NsMe+VLZLjqSjM/KO1JBQa0= =4AT8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi Carlos, I used the command "insserv -r " from command line as a stand alone. Even that is failing to remove entries from depends files. But the symbolic links are removed from all run levels. In my uninstall script, I did not remove the symbolic links through the command "rm", instead I used the command "insserv -r <>" through my script. Hence the symbolic links are actually removed by "insserv" only. Is there anything I have to take care of ? By the way here is the LSB header of my startup script inside /etc/init.d/ ### BEGIN INIT INFO # Provides: aclogrd # Required-Start: $network # Should-Start: # Required-Stop: # Default-Start: 2 3 5 # Default-Stop: 0 1 6 # Description: Security Audit aclogrd Service ### END INIT INFO Thanks, Murali -----Original Message----- From: Carlos E. R. [mailto:robin.listas@telefonica.net] Sent: Friday, June 13, 2008 8:24 PM To: OS-en Subject: RE: [opensuse] clean uninstall -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-06-13 at 09:40 -0400, Kamal, Murali wrote:

Hi Carlos,

The uninstall script that uses "insserv -r " is able to remove all symbolic links from all runlevels.

But the entries from depend.start and depend.stop are not getting deleted !!

I am not sure if I discovered a bug. But I will report to the bugzilla team, who can verify the same with another r application/scenario.

Hold on, hold on. The symbolic links have to be removed by insserv, not by your script. I'm not sure if I understood you correctly, are you doing that :-? The best thing is to try insserv from the command line, directly, and check that it is able to insert and remove the service properly, both the links and the depend entries. Once that is working you put the apporpiate calls in your install scripts or whatever. If it doesn't work standalone it will not work from your scripts, and if everything is correctly done but something fails, it is a bug that has to be reported.

Thanks for all (especially Philipp) your help in this issue and the "Automatic restart of services" issue.

Welcome. :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIUooftTMYHG2NR9URAtQOAJ90iZlufcS6VeGidTlqYwCEaYh3kACeJeCO n5aaLHWfa6K7YMbR7d0XA18= =PaCC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I raised a bug for this in bugzilla. They resolved the issue saying that it is fixed in Suse 11.0. To have clean .depend.* files, we need to execute insserv command without any parameters, so that I will remove unnecessary links from the .depend.* files. This is the response I received from suse dev team: "Please belive me that this is not a problem as startpar(8) ignores not enabled services. The insserv(8) version of openSuSE 10.2 does not clean out the makefiles but list all possible services. To get cleaned makefiles after deintalling simply execute `insserv' without any option:" Thank you all for your support. Regards, Murali. -----Original Message----- From: Carlos E. R. [mailto:robin.listas@telefonica.net] Sent: Saturday, June 14, 2008 12:57 AM To: OS-en Subject: RE: [opensuse] clean uninstall -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-06-13 at 11:00 -0400, Kamal, Murali wrote: ...

By the way here is the LSB header of my startup script inside /etc/init.d/

### BEGIN INIT INFO # Provides: aclogrd # Required-Start: $network # Should-Start: # Required-Stop: # Default-Start: 2 3 5 # Default-Stop: 0 1 6 # Description: Security Audit aclogrd Service ### END INIT INFO

I think you need also: # Required-Stop: $network otherwise, network might be stopped before your service. Try. If the depend files still are not cleared of your service, I think that's a bug. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIUsoGtTMYHG2NR9URAsdcAJ9YoNLvRllIGeZvO7t0vTfmr9Fo3gCdFWve MvMd/UvC9jAYiaWyJGn2+V0= =/z1q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Jun 16, 2008 at 8:13 AM, Kamal, Murali wrote:

Hi all,

I have a service which should be started soon after a reboot.

I have the following header for the script inside /etc/init.d/:

#! /bin/sh # # VeRsIoN: 8.0 (200.125) Compiled On:Jun 13 2008 05:21:17 i86PC # # start/stop eTrust Audit daemon

### BEGIN INIT INFO # Provides: aclogrd # Required-Start: $network # Should-Start: # Required-Stop: # Default-Start: 2 3 5 # Default-Stop: 0 1 6 # Description: Security Audit aclogrd Service ### END INIT INFO

Then I use the command insserv to have the service registered in the boot scripts(depend files). The above command allocates the Start priority of "S06" and stop priority of "K15".

Is there a way I can set my own priority rather than system allocated default priority on Suse 10 zLinux/zOS?

I tried to add the line "# chkconfig: 235 77 23" as Second line of script, but the command "insserv " still takes a default priority of "S06". Will this priority change on different systems ?

The S06 is calculated by virtue of the fact that the script needed the network running before it started. If that is not so, then adjust the script removing the $network. Can you manage your own: Yes. You can build your own links in rc3.d and or rc5.d. But I wouldn't recommend it. -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Jun 16, 2008 at 12:35 PM, Carlos E. R. wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Monday 2008-06-16 at 10:48 -0700, John Andersen wrote:

...

Can you manage your own: Yes. You can build your own links in rc3.d and or rc5.d.

But I wouldn't recommend it.

No, you can't. The next time yast has a look at the services (when you install or remove an rpm with a service) all your symlinks will be removed. And, as a matter of fact, the symlinks are not decisive now, what matters is the contents of the .depend* files.

It was my understanding that the only symlinks managed by suse are those containing the ### BEGIN INIT INFO ### END INIT INFO Blocks. And only those depend on .depend. files. All others (manually created ones) will be left alone and continue to work. Are you saying thats wrong? -- ----------JSA--------- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

...

Yes. You can build your own links in rc3.d and or rc5.d.

But I wouldn't recommend it.

No, you can't. The next time yast has a look at the services (when you install or remove an rpm with a service) all your symlinks will be removed. And, as a matter of fact, the symlinks are not decisive now, what matters is the contents of the .depend* files.

It was my understanding that the only symlinks managed by suse are

So can I conclude that, there is no way to ensure services start at custom priority time on SLES 10 using "insserv" or "chkconfig" from scripts other than writing the symbolic links manually!! -----Original Message----- From: Carlos E. R. [mailto:robin.listas@telefonica.net] Sent: Tuesday, June 17, 2008 4:56 AM To: OS-en Subject: Re: [opensuse] Priority of starting services after reboot on Suse 10 zLinux -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-06-16 at 15:26 -0700, John Andersen wrote: those

containing the ### BEGIN INIT INFO ### END INIT INFO Blocks.

And only those depend on .depend. files. All others (manually created ones) will be left alone and continue to work.

Are you saying thats wrong?

My understanding is that any symlink that is not "properly" managed will be deleted, or at least, it can be deleted. Maybe they are not deleted but overwritten with the new one according to its data. Maybe under some circumstances they may remain. I don't know. What I know is that there is no warranty that they are left alone, not even that they work. I understand that they are not executed if the start/stop sequence runs in parallel mode, but perhaps it is "make" mode. The OP poster found that out, that was his first problem: his scripts did not execute even though he had the correct symlinks. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIVvaTtTMYHG2NR9URAiwiAJ9PwJ9rA+1ZbQoLobDub0Ny+9iYMwCaAlv7 +djkMewSi93UZ3HtKNMTzng= =M1ad -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Philipp Thomas wrote:

On Tue, 17 Jun 2008 12:08:48 -0400, Kamal, Murali wrote:

...

So can I conclude that, there is no way to ensure services start at custom priority time on SLES 10 using "insserv" or "chkconfig" from scripts

Why would you want to load and start executing a service before other necessary services are up and running? In almost all cases, the best thing to do when adding 3rd-party service software is to make it start last, and get killed first (S99 and K00) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, 18 Jun 2008 01:48:35 -0400, Kamal, Murali wrote:

But How do I set my priority to S99 ? Is there a way out without creating the links manually ?

As stated in /etc/init.d/skeleton, use $ALL as Required-Start and the script should start last. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wed, Jun 18, 2008 at 05:12:03AM -0400, Kamal, Murali wrote:

Hi Philipp,

If I do the same, the service is getting created with a priority S20. I don't think this will be constant across all machines. It depends on what kind of 3rd party applns were installed prior to my application.

Again, my question boils down to "How can I set custom priority(for instance S77, S66 etc)? ofcourse my priority is not so stringent it can start after S20 or S50).

The main problem(porting appln from Suse 8/9 to Suse 10) I am facing is that, the rest of the product refers to S77 to start any service.

Hence I need to make sure that insserv will give a start priority of S77 to the services. Is there a way out ?

You can't. But you should just say: "Use '/etc/init.d/service start' to start the service:" and so avoiud the use of S or K levels. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 06/18/2008 05:12 PM, Kamal, Murali wrote:

Hi Philipp,

If I do the same, the service is getting created with a priority S20. I don't think this will be constant across all machines. It depends on what kind of 3rd party applns were installed prior to my application.

No, I don't believe so. If you add $ALL, insserv will ensure it is always last. If by 3rd party you mean apps that do not follow the SUSE way of doing it, any previously done symlinking will be removed when yours is installed and insserv is run.

Again, my question boils down to "How can I set custom priority(for instance S77, S66 etc)? ofcourse my priority is not so stringent it can start after S20 or S50).

You are looking at this incorrectly. You should make sure your Required-Start and Required-Stop lines are correctly filled in, with what your script needs, and insserv will make sure the sym links are correct for the system no matter what else is installed.

The main problem(porting appln from Suse 8/9 to Suse 10) I am facing is that, the rest of the product refers to S77 to start any service.

Hence I need to make sure that insserv will give a start priority of S77 to the services. Is there a way out ?

If you mean documentation, take Carlos' advice and add an rc symlink in /sbin or /usr/sbin, i.e. ln -s /etc/init.d/<name of script> /usr/sbin/rc<name of script>. Otherwise, saying S77 has no relative meaning, except probably towards the end. If yours ends at 20, then 20 is towards the end. S77 is only meaningful as compared to the other scripts in the runlevel directories. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-06-16 at 11:13 -0400, Kamal, Murali wrote:

Hi all,

Notice that you hijacked your own thread ;-)

I have a service which should be started soon after a reboot.

I have the following header for the script inside /etc/init.d/:

#! /bin/sh

Put this as: #!/bin/sh Ie, no space.

# # VeRsIoN: 8.0 (200.125) Compiled On:Jun 13 2008 05:21:17 i86PC # # start/stop eTrust Audit daemon

### BEGIN INIT INFO # Provides: aclogrd # Required-Start: $network # Should-Start: # Required-Stop: # Default-Start: 2 3 5 # Default-Stop: 0 1 6 # Description: Security Audit aclogrd Service ### END INIT INFO

Then I use the command insserv to have the service registered in the boot scripts(depend files). The above command allocates the Start priority of "S06" and stop priority of "K15".

Ok.

Is there a way I can set my own priority rather than system allocated default priority on Suse 10 zLinux/zOS?

Er.... no. The number 6 corresponds to the earlier the system sees as possible _after_ network has started. It is impossible to do it earlier, as yo have requested it to be installed after "network". There is a hook to services to be started before the rest, which are the boot.something scripts. You can see what is there for samples; but be aware that starting before the rest means that almost nothing is running. There will be no network, for instance. Notice that some of the services that start earlier than network are very basic; hald, for instance, or resmgr. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIVsJptTMYHG2NR9URAretAJwKC+WQgmosI/qs8tn7AVqQY+wnqgCfbvuf X3ii3HBcXc1ZboXzvalLPbs= =Pk7d -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org