Elapsed time in --watchfd miscounted on fds opened after a SIGTSTOP/SIGCONT pause
If a --watchfd is running, then is stopped for a short while and resumed, the displayed elapsed time will subtract the amount of time spent stopped, as normal. But, if the watched process opens a new fd, that stopped time is subtracted from its elapsed open time as well, even though it was opened after the stoppage.
For example, if a --watchfd watches a process for a while, then is stopped for a minute, then resumed, the watched process's file descriptors still show their elapsed time counting up as usual, but for any new fds it opens, their elapsed time will sit at 00:00 for 1 minute and only then start counting up.
If a --watchfd is running, then is stopped for a short while and resumed, the displayed elapsed time will subtract the amount of time spent stopped, as normal. But, if the watched process opens a new fd, that stopped time is subtracted from its elapsed open time as well, even though it was opened after the stoppage. For example, if a --watchfd watches a process for a while, then is stopped for a minute, then resumed, the watched process's file descriptors still show their elapsed time counting up as usual, but for any new fds it opens, their elapsed time will sit at 00:00 for 1 minute and only then start counting up.