I am not sure for what and where calendaruserproxy.sqlite and
resourceinfo.sqlite are used? But even I think the location for DataRoot
should be set to /var/lib/caldavd rather than /var/run/caldavd.
Now the question arises what do we do to the two files if they are
already existing for the user in calendarserver 1.2 (lenny)? It should
be noted that rebooting the machine once the system is upgraded to
squeeze will delete these files. Therefore I recommend this solution.
1. Roll out a security update for calendarserver 1.2 (lenny) which
changes the DataRoot to /var/lib/caldavd and moves the files (if they
are existing) from /var/run/caldavd to /var/lib/caldavd.
2. In calendarserver 2.4 (squeeze), change the DataRoot to /var/lib/caldavd.
Do you think there is a better way of handling the problem? If it is
unlikely that users could have stored any permanent data in these two
files in calendarserver 1.2, then we can omit step 1. altogether.
On Thursday 27 January 2011 10:10 PM, Guido Günther wrote:
On Thu, Jan 27, 2011 at 10:00:19PM +0530, Rahul Amaram wrote:
Hi Guido,
What is your opinoin on Bug#611165 (wrong location of
calendaruserproxy.sqlite and resourceinfo.sqlite)? Should I change
the DataRoot to /var/lib/caldavd in /etc/caldavd/caldavd.plist? It
has been /var/run/caldavd since 1.2.
/var/run is not reliable since it gets cleaned (it didn't get cleaned
for Lenny). If these files are needed across reboot you need to move
them.
Cheers,
-- Guido
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
