Free/busy - what triggers it?

[Bernhard Reiter]

Am Dienstag, 31. März 2009 14:12:08 schrieb Chris Hastie:
> I've run through the troubleshooting guide and I can grab free busy data
> if it has been generated. I can also trigger the generation of free busy
> data by hitting the trigger url in a browser, but only for the user I
> log in as (even if that user has read/write permissions on another
> users calendar).

Please state your version of Kolab Server in all reports and questions.
Note that a user can trigger all calender folders with write access.
Otherwise this is a defect in your Kolab Server revision or setup.

> What I don't understand is how this is supposed to get triggered? I've
> had a several users using the system for a couple of months, both
> through Horde and Outlook + toltec, and none appears to ever have
> triggered generation of fb data. Do they have to trigger generation
> manually? Is there a configuration option I've missed somewhere?

http://kolab.org/cgi-bin/viewcvs-kolab.cgi/doc/architecture/freebusy.txt?rev=1.26&content-type=text/vnd.viewcvs-markup
| Whenever a client writes to a calendar it MUST trigger the server based
| generation of fb in the scope of the corresponding folder.

Toltec has a configuration option to enable freebusy triggering
in the account options if I remember correctly. So go to personal folder, 
right click and choose Toltec.

The Kolab Web Client (based on Horde) will also do so, otherwise it is a 
defect.

> I also notice that in Horde's options for Kronolith, a different fb url
> is given, which seems to always return an empty page.

Yes, this page is wrong in several aspects, I've also noticed yesterday:
kolab/issue3519 (freebusy configuration page highly missleading)

Bernhard
-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20090401/6ed3b5e5/attachment.sig>