Project

General

Profile

Actions
Copy link

Bug #5689

closed

AdiIRC should refuse to start if config file or serverlist file is locked/in use

Added by Per Amundsen 10 months ago. Updated 10 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Per Amundsen
Category:
Interface
Target version:
4.4
Start date:
02/25/2023
Due date:
% Done:

0%

Estimated time:
Operative System:
All
Regression:
No

Description

AdiIRC should refuse to start if config file or serverlist file is unaccessible

Actions
Copy link
 #1

Updated by Per Amundsen 10 months ago

  • Status changed from Resolved to Closed
Actions
Copy link
 #2

Updated by eahm eahm 10 months ago

Isn't it better if it starts with default configs if they are not accessible or not present? Or give an error msg? Sorry jumping in, not actually sure what happens when they are not accessible until I test.

Actions
Copy link
 #3

Updated by Per Amundsen 10 months ago

  • Subject changed from AdiIRC should refuse to start if config file or serverlist file is unaccessible to AdiIRC should refuse to start if config file or serverlist file is locked/in use

No, this is for situations where the config file is in use/locked by another program, e.g when starting 2 instances of adiirc at the exact time accidentally etc.

If it started with default options, it would overwrite the config file with these default options at some point, this is to avoid exactly that.

Maybe unaccessible is the wrong word.

I changed it.

Actions
Copy link
 #4

Updated by eahm eahm 10 months ago

Ohh I see, thanks man.

Actions
Copy link

Also available in: Atom PDF