|
From: Alexandre K. <ale...@ta...> - 2014-11-18 01:39:28
|
In case someone else is facing the same issue. On RHEL (CentOS and Fedora), the script file is using "chkconfig". And to set the desired priority you have to modify the following line: # chkconfig: 2345 20 80 Do not remove '#'. "2345" means the run level 2,3,4 and 5. The last 2 numbers are the values for S and K. The RUN_LEVEL parameter is used for other platforms (Solaris, HPUX....). And make sure to uninstall the service first, before editing the script file. Here is a link about chkconfig: http://linuxcommand.org/man_pages/chkconfig8.html Alexandre Klein Alexandre Klein Tanuki Software, Ltd. 6-16-7-1001 Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel: +81-3-3878-3211 Fax: +81-3-3878-0313 http://www.tanukisoftware.com On Fri, Nov 14, 2014 at 8:50 PM, Lars Schnoor <la...@if...> wrote: > Hi > > I am using the wrapper in version 3.5.25 on Linux 32-bit (RHEL 6.3). I > try to get my application to start after another application is started > which is started at run level 50, so I set the RUN_LEVEL parameter to > 60. If I now look in the /etc/rcX.d directories I can see that my > application is started as S24 and stopped as K80. How can I get my > application to be started after run level 50? > > Lars > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > |