> So the WatchedFileHandler is getting triggered when there is something to log in a specific process
RIght, that's what I said in the original description:
> but other processes will continue to hold open the file descriptor until (a) they exit or (b) they write a log message:
Having SIGHUP handling as you've described seems like a reasonable solution. Hopefully that will start to crop up in other services as well.
> So the WatchedFileHandler is getting triggered when there is something to log in a specific process
RIght, that's what I said in the original description:
> but other processes will continue to hold open the file descriptor until (a) they exit or (b) they write a log message:
Having SIGHUP handling as you've described seems like a reasonable solution. Hopefully that will start to crop up in other services as well.