[Dbconfig-common-devel] Re: dbconfig-common Problems

[Miguel Gea Milvaques]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

sean finney wrote:
> hey andreas,
>
> On Fri, Jul 29, 2005 at 10:05:28PM +0200, Andreas Tille wrote:
>
>>On the other hand this does not really change something regarding to
>>the fact that I think something should be changed in dbconfig-common
>>if password authentication *would be* needed.
>
>
> it would be nice to have a way to let dbconfig-common automatically
> add some kind of information to postgresql-server's configuration so
> that manual intervention woulddn't be necessary.  i really don't
> want to arbitrarily mess with important postgres configuration files
> though, hence a dilemma.
>
> however, i think martin pitt has been considering making changes to the
> default postgres configuraiton to allow passwords by default, which
> would make this all moot.
>
> in the meantime, it should at least give informative error messages
> when a method fails; perhaps it should suggest to try connecting
> with another message when it does?

Do you know if there are works about a tool to change postgresql
configuration files? If not, maybe we must ask Martin. I was thinking
about that tool and I think this is not our work.

About the work you said, If there are no works on that tool, I think it
could be a good idea.



- --
e-mail: Miguel Gea Milvaques <debian(@nospam)miguelgea.com
Blog: http://www.livejournal.com/users/xerakko/
GnuPG key: 0x580808C4
Key fingerprint = 85A0 06FD 9A6C 4701 27C2  5536 3533 50CA 5808 08C4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC7KKDNTNQylgICMQRAl/2AJ0anLo1R5xCiKjv+Bpd0h035xj1fgCgyan+
P33VuoEc22XUo3fDFTQuyYw=
=KlAP
-----END PGP SIGNATURE-----