<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body style="font-family: tt;" text="#000000" bgcolor="#FFFFFF"><div
style="font-family: tt;"><span style="font-family: monospace;"></span>Rahul
Amaram wrote:<blockquote
cite="mid:5275250C.3060806@users.sourceforge.net" type="cite">I am
trying to run calendarserver <span
__postbox-detected-content="__postbox-detected-date"
class="__postbox-detected-content __postbox-detected-date"
displaystyle="display: inline; font-size: inherit; padding: 0pt;">5.0</span>
on Debian Jessie. While postgresql
backend seems to work fine, I have been facing issues with files backend
(I have user_xattr enabled). Could some feedback be provided on this? I
am attaching the error.log for reference. The errors with timestamp
<span __postbox-detected-content="__postbox-detected-date"
class="__postbox-detected-content __postbox-detected-date"
displaystyle="display: inline; font-size: inherit; padding: 0pt; color:
rgb(0, 0, 0);">18:31</span> popped up as soon as I started
calendarserver. The errors with
timestamp <span __postbox-detected-content="__postbox-detected-date"
class="__postbox-detected-content __postbox-detected-date"
displaystyle="display: inline; font-size: inherit; padding: 0pt;">18:33</span>
were encountered when I tried to authenticate to
calendarserver.
</blockquote><br><span><span style="font-family: monospace;"> The file
back-end is very much
obsolete[1]. It still exists only because it's used to upgrade very old
servers, and even that will eventually go away.<br>
<br>
-wsv<br>
<br>
</span><br>
<span><span style="font-family: monospace;">[1] For reliability reasons,
we really need a transactional data store, and the file store can't
practically be made to do that.<br></span></span></span><br></div></body></html>