ejabberd - Comments for "Do not overload the acl" https://www.ejabberd.im/forum/28581/do-not-overload-acl en Thank you so much https://www.ejabberd.im/forum/28581/do-not-overload-acl#comment-67145 <p>Thank you so much</p> Fri, 21 Oct 2016 15:45:09 +0000 shabalin8282 comment 67145 at https://www.ejabberd.im When ejabberd is started, it https://www.ejabberd.im/forum/28581/do-not-overload-acl#comment-67144 <p>When ejabberd is started, it has the ACL list empty, then it reads the config file and loads into memory.</p> <p>When you call reload_config, it reads the config file and loads into memory, overwritting existing data. As you noticed, old ACLs are overwritten, but not deleted: the list isn't empty. </p> <p>I see no way to tell reload_config to not overload, or to remove config in memory before reading it.</p> <p>There is a solution: you must be explicit, for example:<br /> First you block him:</p> <pre> acl: blocked: user: - "user2@localhost" - "test" access_rules: c2s: - deny: blocked - allow </pre><p>Later you want to allow again, without restart:</p> <pre> acl: unblocked: user: - "user2@localhost" blocked: user: - "test" access_rules: c2s: - allow: unblocked - deny: blocked - allow </pre> Fri, 21 Oct 2016 09:51:31 +0000 badlop comment 67144 at https://www.ejabberd.im