Ah, the logging is working - seems a byproduct of how you start the plugin instance as the path is relative from where the process working directory is.
I use the scripting connector from Jon00 - if it detects a disconnect, it runs a script that kills and starts the plugin again. However, the logs directory it uses is where the scripting connector is, not where the plugin is
I use the scripting connector from Jon00 - if it detects a disconnect, it runs a script that kills and starts the plugin again. However, the logs directory it uses is where the scripting connector is, not where the plugin is
Comment