[JDEV] Playing with xdb files while jabberd is running.

Thomas Muldowney temas at box5.net
Fri Sep 27 11:14:11 CDT 2002

This all depends on your cache settings, and even with no cacheing I
would call it risky.  Generally the server is an aggressive cacher
because the XDB is used fairly often.  I don't believe the server keeps
file handles open though.  So if the cacheing is in place and you move
or delete the file the cache will be written out to the file when it is
ready, and the user will be back.  Otherwise, the setup might work, but
I wouldn't count on that type of functionality.  It might be better to
hack the transport and just add an admin capability that stores a flag
in the xdb.


On Fri, Sep 27, 2002 at 11:24:28AM -0500, worklists at dovkatz.net wrote:
> Hello, don't ask why this is necessary, but I have a production jabberd process using file-based xdb to store registration info for remote transports (such as toc,yahoo,etc).
> Is there a deterministic behavior of jabberd if I were to move/delete an xdb file while everything is running?  I need to immediately remove users from a remote transport/gateway and while I can boot them by admin-ing the gateway, I need them to be temporarily unregistered so they cannot log back in.  The best solution I can think of is moving the xdb files, without stopping jabberd.
> So, this is really 2 questions.
> 1) Does jabberd keep file handles open (thus will be connected to the inode on disk) to the xdb's even when it's done reading them? If so, moving the file won't help me.
> 2) If [1] is false, then what happens if I move the file? 
> 3) if [1] is true, what happens if i delete the file?
> Thanks in advance
> -Dov
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/jdev/attachments/20020927/f2ac5774/attachment-0002.pgp>

More information about the JDev mailing list