What steps will reproduce the problem? 1. prosodyctl register test my.server.net Somepassword 2. echo 'test@my.server.net=Test User' >> /etc/prosody/groups.txt 3. prosodyctl reload What is the expected output? It is reasonable when the above steps are completed, the new user to appear in the other users's list. But this did not happen at all. What do you see instead? After full restart of prosody server (stop/start), the new user appear. But this lead to disconnects of all active connections. So it is not very comfortable. What version of the product are you using? On what operating system? Server: 0.9.12 OS: Raspbian 7.11; kernel: 4.1.19+ #858 Clients: Conversations for Android; Gajim for Windows Please provide any additional information below.

I believe one can reload mod_groups using either adhoc command or the telnet console, but all affected users still need to relogin, so it doesn't help that much.

• title Batch register users need restart mod_groups: Users must re-login for changes to apply after reload

• tags Status-Accepted Type-Enhancement
• title mod_groups: Users must re-login for changes to apply after reload mod_groups: Ability to apply changes to groups while users are connected