Thanks Aaron. I had been in the /var/lib/pgsql/data folder, to get at the pg_hba.conf file - but I had focused on that one file, I totally missed the postgresql.conf file sitting there as well. Funny though, doing whereis and locate on it didn't find it. (I guess the lesson learned is to NOT be doing sysadmin work in the wee hours of the morning after a long day... <grins>)
I do need TCP/IP as this will be a DB server to one or more web servers. I might be able to disable tcp/ip access for now seeing as the first web server will be on the same box. After seeing your message, I took another look at the default "local" line in pg_hba.conf. It was set up with the "sameuser" option, which isn't applicable in this case. Once I removed it, leaving the line as local all all trust all worked as expected. If I didn't have control over who can access the box locally then I would be changing the "trust" part. Otherwise, I'm on my way. Thanks again Aaron, Szemir, and others that helped out. Shawn On Saturday 26 February 2005 10:15, Aaron J. Seigo wrote: > On Saturday 26 February 2005 03:39, Shawn wrote: > > that postgres is starting without TCP/IP support. This is normally > > turned on in a config file somewhere (in Gentoo, it's > > /etc/conf.d/postgresql , and you set a '-i' in the PGOPTS variable). > > the mainstream linux distros are putting the postgres data > in /var/lib/pgsql/data/ these days, and in there you'll find the > postgresql.conf file. you'll probably find this in there: > > #tcpip_socket = false > > change it to: > > tcpip_socket = true > > this is one of the reasons why i wish Linux distros would stick to > conventions whenever there is no compelling reason not to. it's really not > fair to the users/admins of Linux when the knowledge they acrue is not > transferable, all because some distro maker decides they want to do it some > arbitrarily different way. unfortunately, you've learned the gentoo way of > managing postgresql as opposed to the postgresql way of managing > postgresql. the latter is portable with postgresql, the former isn't. =/ > > > If I remove the "-h localhost" command, I get the typical IDENT > > authentication failed error, but that still stems from the lack of TCP/IP > > support (I hope). > > unless you are accessing the pgsql database from another machine, you > really don't need TCP/IP sockets... what you _do_ need to do is to change > the pg_hba.conf file, however. in szemir's email you'll notice this line: > > local all all trust sameuser > > "local" means "using UNIX sockets", really (or whatever non-TCP/IP mech is > available on the platform you are using). you may wish to use password auth > instead of just blind trust, but ident is probably not what you want in any > case. > > then you don't need to define the host in connect line with -h and all will > be happy. _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
