On 04/30/15 18:41 +0200, hw wrote:
>
>
>Am 30.04.2015 um 16:35 schrieb Bron Gondwana:
>>
>>
>> On Thu, Apr 30, 2015, at 11:10 PM, Bron Gondwana wrote:
>>>
>>> You can't remove the db file from under a rubbing instance, only while it
>>> is shut down.
>>
>> Er, a running instance. Great work autoc
Am 30.04.2015 um 16:35 schrieb Bron Gondwana:
>
>
> On Thu, Apr 30, 2015, at 11:10 PM, Bron Gondwana wrote:
>>
>> You can't remove the db file from under a rubbing instance, only while it is
>> shut down.
>
> Er, a running instance. Great work autocomplete. I'm at decent internet
> again now.
Am 30.04.2015 um 15:10 schrieb Bron Gondwana:
>
> You can't remove the db file from under a rubbing instance, only while it is
> shut down.
I could remove it just fine. Did I create issues doing that which might
show up later?
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Inf
I filtered them with rsyslog.
#cat /etc/rsyslog.d/80-mail.conf
:msg, !contains, "fetching user_deny.db entry"
:msg, !contains, "SQUAT returned"
local6.*-/var/log/syslog
I haven't tried the "bogus file location trick."
On 04/30/2015 10:35 AM, Bron Gondwana wrote:
>
>
> On Thu, Apr 30, 20
On Thu, Apr 30, 2015, at 11:10 PM, Bron Gondwana wrote:
>
> You can't remove the db file from under a rubbing instance, only while it is
> shut down.
Er, a running instance. Great work autocomplete. I'm at decent internet again
now.
You need to shut down Cyrus and restart it for the existi
You can't remove the db file from under a rubbing instance, only while it is
shut down.
On Thu, Apr 30, 2015, at 06:37 PM, hw wrote:
>
>
> Am 29.04.2015 um 20:24 schrieb Dan White:
> > On 04/29/15 18:35 +0200, hw wrote:
> >>
> >>
> >> Am 29.04.2015 um 18:15 schrieb Dan White:
> >>
> Does t
Am 29.04.2015 um 20:24 schrieb Dan White:
> On 04/29/15 18:35 +0200, hw wrote:
>>
>>
>> Am 29.04.2015 um 18:15 schrieb Dan White:
>>
Does this mean that before 2.5.1, the database is being opened and
closed all the time, yielding a log message?
>>>
>>> Correct. But that was an error pro
On 04/29/15 18:35 +0200, hw wrote:
>
>
>Am 29.04.2015 um 18:15 schrieb Dan White:
>
>>>Does this mean that before 2.5.1, the database is being opened and
>>>closed all the time, yielding a log message?
>>
>>Correct. But that was an error produced if the user_deny.db file didn't
>>exist, and ended u
Am 29.04.2015 um 18:15 schrieb Dan White:
>> Does this mean that before 2.5.1, the database is being opened and
>> closed all the time, yielding a log message?
>
> Correct. But that was an error produced if the user_deny.db file didn't
> exist, and ended up flooding syslog. That's a different sy
On 04/29/15 17:21 +0200, hw wrote:
>
>
>Am 29.04.2015 um 16:14 schrieb Dan White:
>>On 04/29/15 16:07 +0200, hw wrote:
>>>Hi,
>>>
>>>is there a way to reduce the log output from cyrus? A lot, if not most,
>>>entries say 'imaps[20670]: fetching user_deny.db entry for ...', which
>>>seems to be a ra
Am 29.04.2015 um 16:14 schrieb Dan White:
> On 04/29/15 16:07 +0200, hw wrote:
>> Hi,
>>
>> is there a way to reduce the log output from cyrus? A lot, if not most,
>> entries say 'imaps[20670]: fetching user_deny.db entry for ...', which
>> seems to be a rather useless information.
>
> Which ver
On 04/29/15 16:07 +0200, hw wrote:
>Hi,
>
>is there a way to reduce the log output from cyrus? A lot, if not most,
>entries say 'imaps[20670]: fetching user_deny.db entry for ...', which
>seems to be a rather useless information.
Which version are you running? 2.4.x changed the behavior of when t
12 matches
Mail list logo
