[Kolab-devel] pfbcache.db locking problems

[Bernhard Reiter]

Am Dienstag, 23. Mai 2006 17:19 schrieb Pieter Vanmeerbeek:

> I was wondering if anyone else got locking problems with gdbm pfbcache.db
> file. If you create an appointment with > 14 resources, all set with
> declines if conflicts, you can simulate it easily.
>
> The lookup of freebusy info just stops as the database is locked by one of
> the other resource handling threads, resulting in nt adding a calendar
> entry for the resource. 

If this is reproducable, please file an issue.
I have not yet tried inviting 14 resources.

> This following line is shown as extra info when I 
> add extra logging and create a dump of info gathered with the
> parse_url($url) statement on line 467 of the kolabfilter/resmgr.php file :
>
>
> <b>Warning</b>:  dba_open(pfbcache.db,cd): Driver initialization failed for
> handler: gdbm: Can't be writer in
> <b>/ub-ver/ub-7.0.0/pkg/php4/lib/php/freebusy/freebusy
> cache.class.php</b> on line <b>41</b><br />
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20060603/518d126b/attachment.sig>