Olivier, The patch is in (r9148).
Thanks, ----- "Olivier LAHAYE" <olivier.lah...@cea.fr> a écrit : > Hi, > > This patch fix system_service so it is more robust against bad service > startup scripts. > I think that this fixes ticket #516 (not sure as this fix only correct > start error message if daemon already running). > > - 1st, it uses /sbin/service if possible so the script runs using a > clean environment. > - 2nd, it if a service is started, it will restart it instead of > trying to do a second start. This prevent bad startup scripts > (systemimager-server-monitord for example) that are not LSB compliant > and fails to start if service is already running. Restarting instead > of doing nothing or trying a second start has also the advantage of > starting the daemon even if there is a PID file and the daemon died > unexpectedly. > > SystemServicesDefs.pm.svn9147.patch (fix system_service() ) > SystemServices.pm.svn9147.patch (adds STATUS definition and fix > POSTGRESS definition (before I forget)) > > > Before the patch, we had the following error when pressing "Monitor > Cluster Deployment" setup if systemimager-server-monitord was already > running. > > --> Executing: /etc/init.d/systemimager-server-monitord start > Starting SystemImager's installation monitoring: si_monitor... > failed. > PID file /var/run/si_monitor.pid exists. Must be already running. > ERROR: Impossible to execute /etc/init.d/systemimager-server-monitord > start at /usr/bin/oscar_wizard line 984 > ERROR: Impossible to start service monitord > at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/Tk.pm > line 247 > > => The monitor windows did not displays. > > After the patch: > starting service systemimager-server-monitord... starting service > systemimager-server-monitord... --> Executing: /sbin/service > systemimager-server-monitord status > Status of SystemImager's installation monitoring: si_monitor... > running. > => return code: 0 --> Executing: /sbin/service > systemimager-server-monitord restart > Stopping SystemImager's installation monitoring: si_monitor... > stopped. > Starting SystemImager's installation monitoring: si_monitor... ok. > => return code: 0 A thread exited while 2 threads were running. > > => The monitor windows did opens successfully. > > Regards, > > -- > Olivier LAHAYE > CEA Saclay > DRT-LIST-DETECS-SSTM > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > > _______________________________________________ > Oscar-devel mailing list > Oscar-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oscar-devel ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Oscar-devel mailing list Oscar-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-devel
