[BlueOnyx:01789] Re: DFIX Critical Update

[Greg Kuhnert]

Hi Gustavo.

Personally, I am running a flat password file - and have been for a long 
time. Theoretically, you can pull that line out on a Blueonyx box - but 
I would still keep the other dovecot restart code in there. My box got 
hammered when dovecot changed the log format. Even with the blocking 
functionality turned off, the dovecot restarts helped to prevent the box 
from totally spiraling out of control.

I will add a check in the next version to skip the dbrecover on Blueonyx 
servers in future.

Regards,
Greg

Gustavo Silva wrote:
>> Hi all.
>>
>> I have had a few issues with NewLinQ. There was a SQL query that was 
>> doing something other than what I intended... I fixed that last night. 
>> I've done a fresh install of BlueOnyx this morning, connected to 
>> NewLinQ, and dfix and denyhosts install is working OK for me today.
>>
>> Sorry for any inconvenience.
>>
>> Regards,
>> Greg.
>>
>> --
>> +---------------------------------------------------------------------+
>> |   / \   Greg Kuhnert, gkuhnert at compassnetworks.com.au               |
>> | <  o  > Compass Networks - Pointing you in the right direction      |
>> |   \ /   Come see us for BlueQuartz / BlueOnyx modules & Support.    |
>> +---------------------------------------------------------------------+
>>
>>   
>>     
> Hi Greg,
>
> One question regarding dfix.sh
> For those who are using the flat text password file, is the dbrecover 
> command that exists in dfix.sh still necessary?
>
> Thanks in advance!!
> Gustavo
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at blueonyx.it
> http://www.blueonyx.it/mailman/listinfo/blueonyx
>