Bug #5689
closed
AdiIRC should refuse to start if config file or serverlist file is locked/in use
Added by Per Amundsen over 1 year ago.
Updated over 1 year ago.
Description
AdiIRC should refuse to start if config file or serverlist file is unaccessible
- Status changed from Resolved to Closed
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.
- 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.
Also available in: Atom
PDF