SQUAT failed and loglevel issue

[lkolchin at univ.haifa.ac.il]

Hi,
This is what people say on kolab list on TSQUAT failed' issue http://www.kolab.org/pipermail/kolab-devel/2005-August/004233.html:

QUOTE:
"It simply means that the foler is not indexed, and the logging is turned on at 
debug level, I have long sicne changed the logging to be at info level it is 
just to much noice otherwise on really busy servers.

you may also want to run squatter -s every night to handle your indexing, nut 
note i do NOT recommend this, it may not be good for your environment so you 
need to test it on testsystems first." 

So I think I need only to tell cyrus to use 'info' loglevel instead of 'debug' (I've already mentioned it).
Anyone know how to do it on SuSE?

Regards,
Leon Kolchnsky 

-----Original Message-----
From: brad [mailto:brad at bradandkim.net] 
Sent: Tuesday, September 20, 2005 4:24 PM
To: לאון קולצ'ינסקי
Cc: info-cyrus at lists.andrew.cmu.edu
Subject: Re: SQUAT failed and loglevel issue

On Tue, 2005-09-20 at 12:33 +0300, lkolchin at univ.haifa.ac.il wrote:
> Hello All,
>  
> I keep getting these kind of messages in my logs, when using horde IMP 
> with Cyrus-IMAP server.
>  
> Sep 20 12:06:24 mail imap[19540]: SQUAT failed to open index file Sep 
> 20 12:06:24 mail imap[19540]: SQUAT failed
>  

As the cyrus user run 'squatter'.

Thanks,

Brad