Fw: [JDEV] using roommaker

[David Sutton]

Hi there,

On Tue, Nov 19, 2002 at 09:45:06PM -0000, Rob Davis wrote:
> 
> Thanks David,
> 
>  I'm pleased the minor Perl changes were useful - you must be running a
>  different version of Perl (probably newer!) than us.
> 
I'm running v5.6.1, so I don't know :)
>
>  I didn't realise that I could create the persistent rooms with Exodus
>  though - I'll give that a try. Do I need to be the admin user specified
>  in jabber.xml?
>
The <sadmin> option is designed for server administrators. It makes the
specified user considered an owner of every room under that service.

Room configuration is available to owners of a room. You can have
ownership one of three ways:

1) Creating the room

2) Being promoted to the owner affiliation by another owner

3) Being a server admin <sadmin>
>
>  (might be worth adding that to the MUC documentation BTW cos I had no
>  idea it was the intended method).
> 
From the FAQ:
Q. What happened to having predefined rooms in the jabber.xml
configuration file?

A. The new system uses the concept of 'Persistent Rooms' When a new room
is created and configured, you have the option to make the room persistent. This
saves all the room configuration and affliation lists into the spool of the
hosting jabber server. All persistent rooms are then recreated automatically
whenever the service is restarted. These rooms will persist until the owner
destroys it.

>  Thanks
> 
>  Rob
> 
Regards,

  David
-- 
David Sutton
Email: dsutton at legend.co.uk
Jabber: peregrine at legend.net.uk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20021119/832a5ee9/attachment-0002.pgp>