[bug #19146] -fprintf returns unreliable result

[James Youngman]

Update of bug #19146 (project findutils):

                  Status:                    None => Invalid                
             Assigned to:                    None => jay                    
             Open/Closed:                    Open => Closed                 

    _______________________________________________________

Follow-up Comment #1:

The errors are now reported, as part of the fix for bug #19416.  The exit
status now also reflects the failure of any I/O.  The -fprintf predicate
still always returns true, since this is probably what the user expects. 
Imagine this example:-

find . -type f -fprint /foo/vanilla-files.txt -o -fprint
/bar/other-files.txt

The intent of the user is plainly to list ordinary files in
/foo/vanilla-files.txt and list everything else (directories, for
example) in /bar/other-files.txt.    If an output error causes -fprint to
fail and /foo is nearly full, then vanilla files will be listed in
/foo/vanilla-files.txt until /foo is full.  After that point, vanilla files
will be listed in /bar/other-files.txt until foo becomes not-full again. 

That seems wrong, so -fprint  and -fprintf will always return true.  I/O
errors will be reported in error messages and will cause the exit status to
be nonzero.

The underlying problem was fixed in another bug, and so this one will be
closed.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?19146>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/