mod_ctlextra delete-and-push-shared

Mahlon — Thu, 16 Aug 2007 21:18:37 +0000

badlop wrote:

[...]

Well, you can destroy all rosters at 3:00 AM in the morning: clean the Mnesia table 'roster'. It's easy to add a command to mod_ctlextra to do this.
It's also possible to improve the pushroster command to first remove all roster items for the user.

[...]

I don't understand the meaning of one-off.

Oh, sorry. I meant writing a standalone .beam or whatever to do the custom roster management rather than tinker inside of ejabberd_ctl, but it sounds like ejabberdctl modifications are the way to go.

badlop wrote:

I don't know what exact problems you are mentioning, so I don't know if they are fixed. ;) If shared-roster works for you, you will save a lot of time in setting mod_ctlextra+roster text files. So let's investigate this possibility before.

I was referring to the presence stuff at http://www.jabber.ru/bugzilla/show_bug.cgi?id=223. There was another bug I saw while trolling around, involving a user modifying a shared roster from within their client -- but I can't find a reference to that one now, of course. ;)

I'd far prefer doing the 'right thing' and go down the shared roster path (assuming the above is no longer a problem), and potentially adding a command to mod_ctlextra like 'push-sharedroster' that wipes current shared roster data, and repopulates it from a text file, along with optional Nicknames. Then I can setup a 3am job that polls our LDAP, builds the file (Employees arranged by their respective department), and runs the ejabberdctl command. Employees might actually like organizing their rosters for once instead of getting them blown away each night. :)

Thanks for the response!

Partial answers

mfoss — Tue, 14 Aug 2007 18:06:01 +0000

Mahlon wrote:

1) Looks like pushroster-all appends to the rosters. How can I purge the roster before pushing a new one?

Well, you can destroy all rosters at 3:00 AM in the morning: clean the Mnesia table 'roster'. It's easy to add a command to mod_ctlextra to do this.

It's also possible to improve the pushroster command to first remove all roster items for the user.

Mahlon wrote:

2) Can I include full names somewhere in the roster file? Our users have been used to them with our jabberd2 manipulations, it would be 'weird' to go to JIDs for them.

Yes, probably improving the command.

Mahlon wrote:

3) Am I even headed in the right direction with your additions to ejabberd_ctl? Would this sort of action be better suited as a erlang 'one-off'?

I don't understand the meaning of one-off.

Mahlon wrote:

4) Or is all this shared roster madness fixed in trunk, including namespace stuff? (I didn't see that it was, but thought I'd ask.)

ejabberd - Comments for "Roster management advice"

mod_ctlextra delete-and-push-shared

Partial answers