[SL] Re: Mandrake 9.1

Thanks Jeffery,

All is now Ok.

However I feel like a RANT, not at you but at the people that put 
distributions together.

How the **** can people get the hang of a great OS when the people 
distributing it can't get their heads together and decide the basics. My case 
in point the location of 'pg_hba.conf':

SQL-Ledger FAQ's - Tells you to search /usr/local
DEBIAN - Installs it in /etc/postgresql/
MANDRAKE - Installs it in /var/lib/pgsql/data

I thought LSB was meant to sort these things out. 

Perhaps the major distro's are more interested in gaining market share and 
locking people into their version by making the versions different so people 
will not move.

NOW THAT SOUNDS FAMILIAR

RANT over. 

Contentious yes!  Wrong place for this, yes!  Made me feel better, yes!

Regards

Steven

 

On Saturday 24 May 2003 00:12, you wrote:
> On Friday 23 May 2003 11:07 am, Steven A.McIntosh wrote:
> > However I then ran across an IDENT Authentication failure. The problem
> > here is that Mandrake doesn't appear to have pg_hba.conf, so the FAQ
> > again couldn't help.
>
> Steven,
>
> The pg_hba.conf file is part of the postgresql implementation and yes
> Mandrake would not remove it (nor would any Linux distributor).  You can
> find it in /var/lib/pgsql/data/pg_hba.conf.  HBA = Host Based Access, btw.
>
> Your problem is that the ident authorization for postgres requires you to
> access postgres using the operating systems login and password.  For
> example, if I am logged in as 'jccann' (linux user), then I need to access
> postgresql using the postgresql account 'jccann'.
>
> Below is some additional info about how I setup my pg_hba.conf file.  It
> may not be too important to you, but I thought I would offer some
> additional info.  Finally, you can read more about Client Authentication in
> the postgresql docs.  Check this link for more info.
>
> http://www.postgresql.org/docs/view.php?version=7.3&idoc=0&file=client-auth
>entication.html
>
> Regards,
> Jeff
>
> Here's the default postgres configuration:
>
> local  all     ident   sameuser
>
> This will allow anyone to connect to postgresql database as long as their
> connection is local (i.e., not using TCP/IP and not from another client
> application besides psql).
>
> Here's how mine is configured to require postgresql passwords for account
> authorization.  The first one allows host connections from the 127.0.0.1 IP
> address, which is your local machine's loopback interface.  The 'password'
> portion requires a valid postgresql user and password to connect.  Note
> that you can provide a user account password using the postgresql utility
> createuser -- try 'createuser -h
>
> host       all         127.0.0.1     255.255.255.255    password
>
> This will allow local client applications like sql-ledger to access
> postgresql using a password-authenticated postgresql user account.  Since
> the auth type is not 'ident', it is not necessary that the postgresql user
> account be the same as the operating system account.

Other related posts: