Known issue symlink (#60)

* Update README.md

Author: kewegner

README.md

@@ -115,11 +115,14 @@ If both are specified, APPSODY_CONTROLLER_IMAGE will be used.
 ## Controller behavior
 
 - As of release 0.2.4 only file related events will trigger ON_CHANGE actions by the controller.  Directory events such as mkdir, rmdir, chmod, etc will not trigger ON_CHANGE actions.
+
 - As of release 0.2.4 a potential problem with how events occuring in the APPSODY_WATCH_IGNORE_DIR are handled has been fixed.  Such events are now preprocessed by the watcher code, rather than post processed once the event reaches the controller.
 
 ## Known issues
 
-If the Appsody stack of interest uses a script file (.sh for example) that is then edited by the `vi` editor while the script is running, the file modification time is not updated on the container file system until the script ends.  What this means is that the ON_CHANGE action is not triggered when `vi` writes the file.
+- If the Appsody stack of interest uses a script file (.sh for example) that is then edited by the `vi` editor while the script is running, the file modification time is not updated on the container file system until the script ends.  What this means is that the ON_CHANGE action is not triggered when `vi` writes the file.
+
+- The use of symlinks within the directories that the controller monitors for file changes might result in undefined behavior.
 
 ## Contributing