[GH-ISSUE #100] Ubuntu network drive mapping from a Windows server issue #78

New issue

Closed

opened 2026-02-26 05:31:15 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 05:31:15 +03:00

Owner

Originally created by @kenhuang on GitHub (Nov 17, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/100

I had mapped a network drive from a windows server as a local drive to Ubuntu system.

Some how any new log did not pick up by the harvester, any suggestion?

Regards
Ken

Originally created by @kenhuang on GitHub (Nov 17, 2013). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/100 I had mapped a network drive from a windows server as a local drive to Ubuntu system. Some how any new log did not pick up by the harvester, any suggestion? Regards Ken

kerem closed this issue

2026-02-26 05:31:15 +03:00

kerem commented

2026-02-26 05:31:16 +03:00

Author

Owner

@kenhuang commented on GitHub (Feb 3, 2014):

Just found this on nodejs api doc:

http://nodejs.org/api/fs.html#fs_fs_watch_filename_options_listener

Availability#

This feature depends on the underlying operating system providing a way to be notified of filesystem changes.

On Linux systems, this uses inotify.
On BSD systems (including OS X), this uses kqueue.
On SunOS systems (including Solaris and SmartOS), this uses event ports.
On Windows systems, this feature depends on ReadDirectoryChangesW.
If the underlying functionality is not available for some reason, then fs.watch will not be able to function. For example, watching files or directories on network file systems (NFS, SMB, etc.) often doesn't work reliably or at all.

You can still use fs.watchFile, which uses stat polling, but it is slower and less reliable.

@kenhuang commented on GitHub (Feb 3, 2014): Just found this on nodejs api doc: http://nodejs.org/api/fs.html#fs_fs_watch_filename_options_listener Availability# This feature depends on the underlying operating system providing a way to be notified of filesystem changes. On Linux systems, this uses inotify. On BSD systems (including OS X), this uses kqueue. On SunOS systems (including Solaris and SmartOS), this uses event ports. On Windows systems, this feature depends on ReadDirectoryChangesW. If the underlying functionality is not available for some reason, then fs.watch will not be able to function. For example, watching files or directories on network file systems (NFS, SMB, etc.) often doesn't work reliably or at all. You can still use fs.watchFile, which uses stat polling, but it is slower and less reliable.

kerem commented

2026-02-26 05:31:16 +03:00

Author

Owner

@msmathers commented on GitHub (Aug 1, 2014):

Log.io currently doesn't support harvesting on windows machines... In your case, if the log files are located on a Ubuntu system I'd recommend installing the harvester on the Ubuntu machine itself.

@msmathers commented on GitHub (Aug 1, 2014): Log.io currently doesn't support harvesting on windows machines... In your case, if the log files are located on a Ubuntu system I'd recommend installing the harvester on the Ubuntu machine itself.

kerem referenced this issue

2026-02-26 05:31:42 +03:00

[PR #78] [CLOSED] Folder support added to logStreams #241