This is a note that was sent to me from one of our systems admins.
Is there a fix for this, or can this be fixed?
> The ADSM command line client doesn't properly flush its standard output
> stream before issuing an error diagnostic to standard error. The result
> is that, in the common case where the two streams are directed to the same
> file or same pipe (i. e., to email), the error message is injected into the
> middle of text buffered for the standard output stream. See below.
>
> > Incremental backup of file system: '/var/apps'
> > Normal File--> 275,920 /var/apps/locate/locatedb .....ANS4071E
> > Invalid domain name entered: '/var/apps/nameserv/work'
> > Sent
> > Successful incremental backup of '/var/apps'
>
> Notice the ANS4071E diagnostic in the middle of a line about other activity.
> Not only does this obscure this other text, but it also conceals the presence
> of a diagnostic condition by placing the diagnostic in the middle of the line.
>
> If ADSM issued a buffer flush on the standard output stream before any
> diagnostic message was issued, this problem would go away and the output
> would look as follows:
>
> > Incremental backup of file system: '/var/apps'
> > Normal File--> 275,920 /var/apps/locate/locatedb ..... Sent
> > ANS4071E Invalid domain name entered: '/var/apps/nameserv/work'
> > Successful incremental backup of '/var/apps'
>
> It would thus be very easy for a human or program scanning ADSM output
> to detect the error due to its proper positioning at the beginning of
> the line.
>
> I am using the command line interface, version 2, release 1, level 0.0
> and server version 2, release 1, level 0.8. This problem occurs for
> all clients I use, though the specific example above used the AIX client
> on a system running AIX 3.2.5.
Submitted by R. Booth
|