>-----Message d'origine----- >De : [email protected] >[mailto:[email protected]]de la part de Davide Libenzi >Envoyé : lundi 28 septembre 2009 16:27 >À : XMail Users Mailing List >Objet : Re: [xmail] CtrlClnt local/remote diff in return value on w2k > > >On Mon, 28 Sep 2009, CLEMENT Francis wrote: > >> >> Test with ctrlclnt version 1.26, 1.25 and 1.24 localy on >> >server running >> >> xmail server 1.26 (same ctrlclnt cmd line, same ctrl ip/port >> >and action) >> >> >> >> 1.26 : all ok except delay 30s return code = 1073807364 >> >> 1.25 : all ok except delay 30s return code = 1073807364 >> >> 1.24 : all ok except delay 30s return code = 1073807364 >> >> >> >> Same versions on remote station : all ok, no delay, returns 0 >> > >> >What do you mean for "return code"? The CtrlClnt process exit code? >> >> Yep, ctrlclnt process exit code that you can test in batchs >with errorlevel >> variable on win systems. > >Hmmm ... CtrlClnt never returns such high error codes. Does it crash? >Looks like some sort of error code returned by the system >under certain >abnormal conditions ... > > >- Davide > >
As said, ctrlclnt don't crash at all, at end of job (action correctly completed at xmail server side, and ctrlclnt output correct and complete, nothing missing), it seems to 'freeze' for about 30 seconds (waiting for a timeout ?) before ending then returns normally (no crash dump, no drwatson, no system event in logs, ...) but returns this 'strange' exit code. Same command from a workstation, do the same job, don't freeze at all after final output result, and return 0 I need to test older ctrlclnt versions to find last that work 'localy' with exit code 0 Francis _______________________________________________ xmail mailing list [email protected] http://xmailserver.org/mailman/listinfo/xmail
