https://dev.adiirc.com/https://dev.adiirc.com/favicon.ico?14868454782023-02-25T02:03:08ZAdiIRC Support/Bugs/Feature RequestsAdiIRC - Bug #5689: AdiIRC should refuse to start if config file or serverlist file is locked/in usehttps://dev.adiirc.com/issues/5689?journal_id=103002023-02-25T02:03:08ZPer Amundsenamundsen@gmail.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul> AdiIRC - Bug #5689: AdiIRC should refuse to start if config file or serverlist file is locked/in usehttps://dev.adiirc.com/issues/5689?journal_id=103022023-02-25T05:01:19Zeahm eahm
<ul></ul><p>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.</p> AdiIRC - Bug #5689: AdiIRC should refuse to start if config file or serverlist file is locked/in usehttps://dev.adiirc.com/issues/5689?journal_id=103032023-02-25T05:12:18ZPer Amundsenamundsen@gmail.com
<ul><li><strong>Subject</strong> changed from <i>AdiIRC should refuse to start if config file or serverlist file is unaccessible</i> to <i>AdiIRC should refuse to start if config file or serverlist file is locked/in use</i></li></ul><p>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.</p>
<p>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.</p>
<p>Maybe unaccessible is the wrong word.</p>
<p>I changed it.</p> AdiIRC - Bug #5689: AdiIRC should refuse to start if config file or serverlist file is locked/in usehttps://dev.adiirc.com/issues/5689?journal_id=103042023-02-25T19:18:55Zeahm eahm
<ul></ul><p>Ohh I see, thanks man.</p>