Linux.com

Comment Bug

Posted by: Andrew Yates on October 18, 2008 07:49 PM
As a word of warning, I found that comments inside match scopes caused fsniper to crash on startup, and comments above match scopes caused fsniper not to execute the directory scope correctly. I tried this with tab-indented and non-indented comments; the only way to get the correct behavior was to strip out the comments completely.

This was a regression in v1.3 caused by some new config validation code. It should be fixed as of v1.3.1, which was released earlier today.

#

Return to Automatically process new files with fsniper