hi Richard,
In this context I am also curious, what would be the effect of using
> --check-timeout / --poll-timeout, if the log file will be closed or remain
> open during timeout... I am trying to find a way, how to use SEC in "close
> after read" mode - used to use this mode in previous log
In this context I am also curious, what would be the effect of using
--check-timeout / --poll-timeout, if the log file will be closed or remain
open during timeout... I am trying to find a way, how to use SEC in "close
after read" mode - used to use this mode in previous log event correlation
hi Risto,
thank you for your helpful explanation about inner functionality of SEC.
Closed files in my case were not existing, that was the reason.
Richard
ut 4. 2. 2020 o 23:09 Risto Vaarandi napísal(a):
> hi Richard,
>
> I have never used SEC for monitoring files on NFS file systems, but I
hi Richard,
I have never used SEC for monitoring files on NFS file systems, but I can
provide few short comments on how input files are handled. After SEC has
successfully opened an input file, it will be kept open permanently. When
input file is removed or renamed, input file is still kept open
Hi Risto and friends,
I am unsure about one conceptual question about how SEC keeps open
monitored files.
Using SEC as systemd service, when files stored in NFS (opened via
addinput) being watched by SEC are moved elsewhere, and then their removal
is tried, NFS persistently keeps .nfsNUMBER
