I'm guessing no one else has seen this issue? Most exit codes are properly reported (e.g. code 12, code 10, code 2). The specific scenario is when a filename too long or directory not present error causes the client to exit with a code of 23 (reported as the exit code on the client properly and captured in the environment variable there). The exit code of the server still shows an exit code of zero. Any comments or ideas on what I may be doing wrong? Also, if anyone has comments on what section the code sets the environment variable errors I'd appreciate it.thanks. Rob -------------- next part -------------- HTML attachment scrubbed and removed
Wayne answered in my separate post...ignore this message. Rob "Rob Bosch" <robbosch@msn.com> wrote in message news:<BAY109-DAV15CB6414B299E32B4574E4CF230@phx.gbl>...> I'm guessing no one else has seen this issue? Most exit codes areproperly> reported (e.g. code 12, code 10, code 2). The specific scenario iswhen a> filename too long or directory not present error causes the client toexit> with a code of 23 (reported as the exit code on the client properlyand> captured in the environment variable there). The exit code of theserver> still shows an exit code of zero. Any comments or ideas on what I maybe> doing wrong? > > > > Also, if anyone has comments on what section the code sets theenvironment> variable errors I'd appreciate it.thanks. > > > > Rob > > > > > >
Reasonably Related Threads
- Clarification on the RSYNC_RAW_STATUS and RSYNC_EXIT_STATUS
- Regarding: unable to make USB-ZIP using rufus_v1.4.5
- Error cargar datos ACCESS
- Bug#602378: xen-hypervisor-4.0-amd64: Live migration of Guests crashes and reboots
- Bug#602378: Please can you try 4.1 from Wheezy