Project

General

Profile

Bug #1980

Client should refuse to use the same userdir as another already running client

Added by vermil almost 10 years ago. Updated almost 5 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Defect
Target version:
Start date:
2015-02-16
% Done:

0%


Description

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 "%
HOMEPATH%\Documents\Doomsday Frontend\runtime\configs"
^ : Terminated by signal


Related issues

Related to Bug #2055: [MP] Multiple instances can't connect to a local serverNew2015-05-16

Related to Feature #2057: Multiple client instancesNew2015-05-16

History

#1 Updated by vermil almost 10 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 almost 10 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.

#3 Updated by skyjake almost 10 years ago

  • Subject changed from Crash with multiple clients when quitting to Fatal error when quitting with multiple local client instances (same userdir)

#4 Updated by skyjake over 9 years ago

  • Priority changed from Normal to Low

#5 Updated by skyjake over 9 years ago

  • Related to Bug #2055: [MP] Multiple instances can't connect to a local server added

#6 Updated by skyjake over 9 years ago

#7 Updated by skyjake over 7 years ago

  • Category set to Defect
  • Target version set to 2.1 (Late 2018)

#8 Updated by skyjake about 6 years ago

  • Target version changed from 2.1 (Late 2018) to 2.2 (2019)

#9 Updated by skyjake about 5 years ago

  • Target version changed from 2.2 (2019) to 2.3.x

#10 Updated by skyjake almost 5 years ago

  • Subject changed from Fatal error when quitting with multiple local client instances (same userdir) to Client should refuse to use the same userdir as another already running client

Also available in: Atom PDF