linux filewatcher remove spaces from filename

Reading the answers, it is obvious that there are cases where FSW covers the needs perfectly, while other times, you need polling. I am, currently, trying to decide whether I will use FSW or polling for a project I develop. If you need to use polling to check for any 'FSW misses', then you can, naturally, discard FSW altogether and use only polling. Using both FSW and polling is a waste of time and resources, in my opinion, and I am surprised that experienced developers suggest it. This has been in production without error for about two years. We also read all the files before beginning to process even one.get the file names safely cached away (in our case, into a database table) then process them.įor file locking issues I spawn a process which waits around for the file to be unlocked waiting one second, then two, then four, et cetera. We use 16MB due to a large batch expected at one time. To avoid a buffer overflow, use the NotifyFilter and IncludeSubdirectories properties to filter out unwanted change notifications. Increasing buffer size is expensive, as it comes from non paged memory that cannot be swapped out to disk, so keep the buffer as small as possible. It does use memory that cannot be paged out, so it could force other processes to page if memory gets low.įileSystemWatcher.InternalBufferSize Property Remember that it contains the file names and events, so increase it to the expected amount of files (trial and error). Easy as pie to fix-just increase the buffer.

The biggest problem I have had is missing files when the buffer gets full.

Linux filewatcher remove spaces from filename