Log In     Register    

DarkMX Support Forum
Questions and comments about the software
<<  Back To Forum

Running several darkmx instances for different users on the same

by Guest on 2023/11/08 09:31:19 PM    
As per subject on linux are there some cmd line switches that allow breaking out of single app instance pattern?
by Guest on 2024/01/06 10:54:42 AM    
look at https://darkmx.app/run_mode

Put the darkmx executable into it's own folder with darkmx_local_instance_check.txt (empty text file) and when it starts up it will be single-instance but only from that specific folder.  Make another folder the same way, and it can run in a separate instance.  The config files will be stored in the folder with the executable, so your two instances will have completely separate configs, user name, etc.
by Guest on 2024/01/06 04:36:36 PM    
Consider the use case. One want two profiles to separate activities. The app is updated throgh system regular update routine. Only default configuration up to date. To prevent several big copies of the executable and keeping them up to date, wouldn't be much better the approach of command line parameters where you can tell either an alternative config file or directory to run, plus also optional switches that could be added as outlined on the page.
by notaLamer on 2024/01/07 03:24:36 PM    
The dev seems to be afraid of command line switches, Tixati mostly had local .txt files too :-P
Are you sure that the local files don't work as you want them to? I'm pretty sure that "same folder that contains the program" is actually describing the current working directory aka `pwd`. You still get to run the up-to-date system executable but with local data.
by Guest on 2024/01/07 03:57:51 PM    
looks like it's now added for linux: https://darkmx.app/config_path
by Guest on 2024/01/07 06:31:17 PM    
Are you sure that the local files don't work as you want them to? I'm pretty sure that "same folder that contains the program" is actually describing the current working directory aka `pwd`. You still get to run the up-to-date system executable but with local data.

I'm pretty sure on linux it is reading the path of the running program from /proc.  Not current working directory.  You can confirm by starting it via a relative path on the command line.  This might be different on the other platforms.




This web site powered by Super Simple Server