You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a weird problem (with a workaround hack, see below) at my client. Changes that the logging system on JBoss make to my log files are not caught by the fs.watch(dir) function, hence I get no input in node-logstash. I get the feeling this could be Java file writing that bypasses the Windows stuff that sends events via ReadDirectoryChangesW, but I have no backing for this (Google wasn't my friend today...).
So, I hacked a bit in directory_watcher.js and added an fs.watchFile(...) on each of the files in dir, and every 5 sec (configurable polling interval on watchFile) I get an event. Interestingly, this triggers the fs.watch(...) functionality, so I don't need to do anything in the fs.watchFile(...) handler function.
Has anyone seen anything like this? Any better workarounds?
The text was updated successfully, but these errors were encountered:
I have a weird problem (with a workaround hack, see below) at my client. Changes that the logging system on JBoss make to my log files are not caught by the fs.watch(dir) function, hence I get no input in node-logstash. I get the feeling this could be Java file writing that bypasses the Windows stuff that sends events via ReadDirectoryChangesW, but I have no backing for this (Google wasn't my friend today...).
So, I hacked a bit in directory_watcher.js and added an fs.watchFile(...) on each of the files in dir, and every 5 sec (configurable polling interval on watchFile) I get an event. Interestingly, this triggers the fs.watch(...) functionality, so I don't need to do anything in the fs.watchFile(...) handler function.
Has anyone seen anything like this? Any better workarounds?
The text was updated successfully, but these errors were encountered: