Bruno Et all,
Yea as I looked at it the problem was well defined and the solution popped
out. It was the "local" line in pg_hba and authentication changed from
"ident" to "md5" fixed the problem.
Mehma
===
On Sat, Mar 27, 2010 at 2:23 AM, Bruno Friedmann <br...@ioda-net.ch> wrote:
> On 03/25/2010 01:35 AM, mehma sarja wrote:
>
> > Mehma
> >
>
> Hi Mehma, just take a long breathe, and check with postgresql documentation
> how about interact pg_hba.conf and pg_ident.conf
> to check manually issue a su bacula and try a psql -U bacula -d bacula type
> the password when requested and see if you can
> connect. After you will have a valid connection, bacula-dir can also.
>
> I'm thinking your are mixing normal authorization in pg_hba.conf and
> mapping users in pg_ident.conf
>
>
> --
>
> Bruno Friedmann
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
