Christian, my personal opinion, for what it's worth, would be for vmcp to print an error message of some sort to stderr, if the vmcp commands fails. Besides the 0 and ENOBUF (105) return values, what other codes can vmcp product?
DJ Christian Borntraeger wrote: > Rob, > > I forgot that comment: > >> It's annoying to silently truncate the response, so should you not >> write something into stderr to point that out? > > vmcp has a return value, which you can check in scripts. > e.g: > > # vmcp <some large query> > # echo $? > > 0 stands for everything is fine, any other value for problems. > vmcp returns ENOBUFS (105) if the buffer was not large enough > That means the output was larger than 64kb. > > You can also print a message using the or code in shells: > > # vmcp <some large query> || echo "error code: $?" > > If there is a consensus that vmcp should always print something > to stderr if the buffer was not large enough, tell us and we can > add that. > > > > > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
