mirror of
https://github.com/NarrativeScience-old/log.io.git
synced 2026-04-26 01:25:55 +03:00
[GH-ISSUE #231] The file which is mounted (using NFS )on a server cannot be monitored. #187
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/log.io-NarrativeScience-old#187
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @harlanc on GitHub (Apr 9, 2020).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/231
I mounted a folder A from machine AA to folder B on machine BB using NFS , and I launched a log.io-file-input client on machine BB after the log file path is configured correctly.
~/.log.io/inputs/file.json
But the log content changes cannot be displayed on the browser.
BTW, the common log file on machine BB can be monitored successfully.
@msmathers commented on GitHub (Apr 9, 2020):
log.io uses node's
fs.watch()to watch for file changes, which is known to not support NFS: https://nodejs.org/docs/latest/api/fs.html#fs_availabilityfs.watchFile()could work, however it uses stat polling which is less efficient thaninotifyand uses more system resources.Unfortunately we don't plan to support anything other than
fs.watch()inlog.io-file-input, however you're welcome to write a custom input that hits our TCP API. Feel free to use the file input code as an example.