Client should refuse to use the same userdir as another already running client
When one has more than Doomsday client running on their computer at once, one get's an illegal operation message on closing one of them.
I pulled this out the out file:
^ > Mus_Start > M_Mus2Midi: Failed opening output file "dd-buffered-song1.mid"
MasterWorker: Received 7 servers from mas^ : Starting music 'titl'
ed to replace renderer.dei: existing file could not be removed.
[RemoveError] (DirectoryFeed::removeFile) Cannot remove "renderer.dei" in directory "%
^ : Terminated by signal
#1 Updated by vermil over 7 years ago
Certainly, I imagine it's because Dday tries to write to or remove files already in use.
To deal with such, Dday would literally have to be aware of how many instants of Dday is open and map each to separate files (i.e doomsday.out, doomsday1.out, doomsday2.out etc etc).
But the practically...
#2 Updated by skyjake over 7 years ago
At present time, if one is running multiple instances of the client locally, it is the user's responsibility to set a unique runtime folder for each (with "-userdir" on the command line).
The bug here is that the client should detect whether another instance is running on the userdir and refuse to launch.
A feature request could be that the client would automatically create a suitable userdir (perhaps by adding a suffix). This would mean, though, that all the persistent state of the first instance is not shared.