|
From: Leif M. <le...@ta...> - 2004-02-25 15:57:00
|
Jocke, This is actually a known problem with 3.0.5 and earlier versions. Due to a misunderstanding in the way that portion of the NT Service Manager API worked, I was not exiting the Wrapper correctly in the event of a non-zero exit code. This has been resolved and will be in the 3.1.0 release. If you are able, you can build a snapshot from CVS to get this fix early. Cheers, Leif my Mailer wrote: >Hi all! > >I know this has been a topic before but when I’m >reading earlier mails, the documentation and running a >few tests I don’t get it all. In W2k one could set the >service to restart if it fails (in the recovery tab). >My guess is that the return code from the service >determines if the service has failed or not when >stopping. The stop method from the WrapperListener >returns the exit code for the service. If it returns 0 >everything works the way I want, the service stops >correctly. But if the exit code is not zero, that >should indicate that something is wrong and the >service should be restarted, but it doesn’t. Instead, >if the exit code is 1 the service stops and in the W2k >Event Viewer shows the description of the exit code >(in this case ‘Incorrect function’). > >Is it possible to get the Wrapper to return the code >to the Service Control Manager in a way that the >service will be restarted? > >Thanks in advance, > >/Jocke > > >Höstrusk och grå moln - köp en resa till solen på Yahoo! Resor på adressen http://se.docs.yahoo.com/travel/index.html > > >------------------------------------------------------- >SF.Net is sponsored by: Speed Start Your Linux Apps Now. >Build and deploy apps & Web services for Linux with >a free DVD software kit from IBM. Click Now! >http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click >_______________________________________________ >Wrapper-user mailing list >Wra...@li... >https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > |