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<service_name> 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