That was my first question too Jim.
Existing users (prior to a change) would stay in /etc/passwd and shadow
files etc. New users would get created in db files.
Solution: There needs to be a item in the BQ database that specifies the
default method for new user creation - db or passwd file etc. Future
updates would look at this, and we'd be happy.
Anyone feel like coding this? <grin>
Jim Scott wrote:
> Just curious. Since you are making changes to BlueQuartz files what
> happens the next time an update gets pulled down that changes one of
> those files?
>
> Jim
>
> ----- Original Message ----- From: "Brian N. Smith" <brian (at mark) nuonce.net>
> To: <coba-e (at mark) bluequartz.org>
> Sent: Wednesday, July 25, 2007 3:51 PM
> Subject: [coba-e:10445] Re: Dovecot Authentication failure
>
>
>>> Any update for the Dovecot Authentication failure problem?
>>> Yesterday my blueq too many ftp login connection (succeed)
>>> FTP server is going down later many ftp login,
>>> I check the log, see the dovecot err in same time. I need off the
>>> cce and
>>> run /etc/rc.d/init.d/dbrecover to fix
>>>
>>> Any solution for fix?
>>
>> I have a good work around that I have been playing with. Knock on
>> wood, it works for ME. I will make this single claim. DO THIS AT
>> YOUR OWN RISK. If you follow the steps, it SHOULD work just fine.
>>
>> What does it do? It converts the password database back to a flat
>> file instead of keeping it in the DB format.
>>
>> http://www.nuonce.net/bq-howto.php?action=view&id=23
>>
>> It will also modify the BlueQuartz backend so that it writes to the
>> /etc/passwd file as well.
>>
>> Remember .. DO THIS AT YOUR OWN RISK. If you attempt it, you release
>> NuOnce Networks, Inc. from any and all liability.
>>
>> Thanks!
>> Brian
>>
>>
>
>
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.