[Rt-devel] output on stderr and not using return values

Jesse Vincent jesse at bestpractical.com
Wed Dec 26 16:22:03 EST 2007

On Fri, Dec 21, 2007 at 05:47:10PM +0100, Camenzind Patrick (KSDB 533) wrote:
> I just started using the RT(v3.6.3) command line interface for scripting
> purposes and was wondering why it doesn't make use of return values at
> all, means wether a command was successfully done or not can only be
> recognized by comparing the output strings on /dev/stderr as it always
> returns zero as returnvalue... this leads me directly to my second
> question: why not using /dev/stdout for outputs instead? It took me
> about one day to figure out why my string comparison didn't work :-( 

I'd love a patch to offer sane return values.  As to why we're using
STDERR rather than STDOUT,  the best I can offer is to plead "historical


> any ideas?
> Regards
> Patrick
> _______________________________________________
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
> If you sign up for a new RT support contract before December 31, we'll take
> up to 20 percent off the price. This sale won't last long, so get in touch today.
>     Email us at sales at bestpractical.com or call us at +1 617 812 0745.


More information about the Rt-devel mailing list