I suppose this output operation needs error checking (write an error message to stderr, make sure the exit status is not 0 and (whatever GNU find does) either stop immediately or continue without writing anything more to this file. Also, there probably should be fclose with error checking before exiting (near or in finish_execplus).

By the way, GNU find does not flush -fprint files when executing subprocesses unless it's -fprint for /dev/stdout or /dev/stderr, so we shouldn't either (it slows down things).

This means that multiple -fprint primaries to the same file will typically not work properly. I'm not sure we care. GNU find seems to concatenate all such output together, even if the -fprint primaries contain different hard links to the same file.

I'll take a look at what they do... We shouldn't flush fprintf either...
I'm not sure I follow about first error closing the file with checking... Please elaborate on why that's a good idea or the thinking behind it... it would be good to have in a comment and something better than 'imitate what gnu find does' would be ideal.

Hmmm... that's a bit surprising if true. I'll double check gnu find's behavior... multiple -fprints seems a bit odd... But maybe not too odd...