<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div style="font-family:Arial;">I've just pushed some changes to Cassandane to scan syslog for known "badness" (basically anything with ERROR in it for now, but it's easy to add other things).<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">Unfortunately, that does require that the cyrus user can access the syslog. I've added the template to cassandane.ini.example to choose which file to look at, default is /var/log/syslog.<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">On my Ubuntu machine I just ran "adduser cyrus adm" to grant it access - I'm sure there's similar tricks on other machines, or syslog can be set up to send just cyrus data to a special file and point cassandane there.<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">This
allows Instance to watch syslog and die if there are any unhandled
IOERROR / DBERROR / SYNCERROR lines, which picks up new sets of bugs
automatically :) There are a couple of cases already where I've put in
tests which drain the syslog ($self->{instance}->getsyslog) and
check for the errors they expect. There will need to be more, so some
tests will be failing right now.<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">Cheers,<br></div><div style="font-family:Arial;"><br></div><div style="font-family:Arial;">Bron.<br></div><div style="font-family:Arial;"><br></div><div id="sig56629417"><div class="signature">--<br></div><div class="signature"> Bron Gondwana, CEO, Fastmail Pty Ltd<br></div><div class="signature"> brong@fastmailteam.com<br></div><div class="signature"><br></div></div><div style="font-family:Arial;"><br></div></body></html>