+4
Fixed
When using -Duser.dir switch, a few oddities
When you use the -Duser.dir switch for java to move the working directory, the LOGS directory does not follow the rest of the files.
Also, the webadmin.cred file doesn't know where to go so it ends up in the root directory. Can these be updated to obey that switch? (great app so far!)
Also, the webadmin.cred file doesn't know where to go so it ends up in the root directory. Can these be updated to obey that switch? (great app so far!)
Customer support service by UserEcho
I will probably fix it. However you can easily (and in a more reliable way) ensure that all files will be created in a specific directory by going into this directory before launching Ubooquity.
For instance if Ubooquity.jar is in /home/pi/apps and you want it to create its files in /home/pi/data, just "cd" into "data" before calling java:
Much easier and safe.
Let me know if you have a use case that can not be solved this way (really curious).
Thats where using Duser.dir comes in very handy as users can move those files with ease through my plugin interface. With the cred fike in root, it will be deleted upon reboot of the system, and logs will be lost since it too doesnt use the duser.dir switch. :)
Assuming Ubooquity is launched through a script by the plugin, wouldn't it be possible to use a variable for the working directory that would allow the user the same flexibility as an explicit command line argument ?
Something like:
I'am asking because using the "user.dir" setting is not a completely reliable solution (hence the bugs you encountered). So if there is a real need for a working directory setting, I'll implement it in the code itself. But I really want to be sure that this work is required as for all use cases I have been told about (except perhaps yours, hence my questions), the "cd into another dir" method was enough to solve the problem.