Hello tee developers, I have come across a situation where it would be very beneficial if tee could reopen/recreate a file each time it starts writing to it. So, e.g. logrotate could move away the log file and the file would get recreated on the next output to write to. My issue described here: https://stackoverflow.com/questions/63286536/avoid-sparse-files-with-tee-and-logrotate
Currently tee continues to write to the deleted inode. And it creates sparse files if the file it writes to gets "truncate -s 0" - although tee -a seems to prevent this. Thanks, Alex.
