Hi,
Yup that is exactly what is happening, the file is being renamed to xyz.log.1, hence the issue.
Your sugestion is valid but I'd prefer to have something that is intelligent enough to know that the filename has changed and then reopen the filehandler, as opposed to any outside help. Something along the lines of checking the name of the file that the inode refers to to verify that it is still the expected filename.
Thanks for your suggestion
Jon
I have no experience with it, but how about trying file test operator -C
which gives you 'Age of file (at startup) in days since inode change.'
I'm hoping for 'since inode change' ...