Here's what I got now Aaron... <br>> local all ident sameuser <br> <br>change this to password
When I made that change, and had created a user "root" with pw "root", I could run "psql template1" and would be in without being asked for a password? But if I set it back to password, and try again with "psql" or "psql template1" followed by a password prompt but would get an error even if I gave it the right password? psql: FATAL 1: Password authentication failed for user "root" I still cant get anywhere with mypgadmin, or pgaccess. But will wait until this basic authentication is worked out. Really, this should not be this difficult and as more and more open-source tools and applications become "owned" or supported by larger corporations I would suspect that much like all other things once free, or which provided some sort of expected functionality, performance or feature, we may see more of this as a way to encourage the support and services of the commercial versions. A big pet peeve of mine and it applies to all sorts of things.....even "Hamburger Helper" but thats really way off topic.... Thanks for the suggestions Aaron, and dont worry about trying to help much more with this....I am tired, frustrated and disapointed. I will stick with MySQL and Oracle for now, or until I can commit the time to start learning about postgres authentication from the begining again. <hr> <b><font color=blue size=4>Open Enterprise Solutions</font></b> <b><font color=red>Linux & Open Source Solutions for Business</font></b> Johnny Stork, BA Calgary, AB Canada <a href="http://www.openenterprise.ca";> www.openenterprise.ca</a> ------ original message ------ From: "Aaron J. Seigo" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent: Wed Feb 19 17:25:27 MST 2003 Subject: Re: (clug-talk) Postgres Gurus? <br> <br> <br>> host all 192.168.1.0 255.255.255.0 trust <br>> <br>> TYPE DATABASE IP_ADDRESS MASK AUTH_TYPE AUTH_ARGUMENT <br>> host all 192.168.0.0 255.255.0.0 password <br> <br>looks good, except the trust thing ;-) i don't even trust nobody (unix humour. <br>ha ha. *sigh*) <br> <br>> And when I su to a regular user and try to run postgres command line, I get <br>> a message about "postgres does not know where to find the database......." <br> <br>do you get: <br> <br>psql: FATAL 1: Database "username" does not exist in the system catalog. <br> <br>if so, that's because you need to either create a db for that user or do "psql <br><dbname>" <br> <br>other things to check: postgresql.conf... if tpip_socket isn't set to true, <br>you will only be able to connect locally ... if your web admin stuff is <br>attempting to connect via a TCP hostname (even localhost IIRC) it won't work <br>unless you have tcpip_socket = true... <br> <br>- -- <br>Aaron J. Seigo <br>GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 <br> <br>KDE: The 'K' is for 'kick ass' <br><a href="http://www.kde.org"target="top";>http://www.kde.org</a> <a href="http://promo.kde.org/3.1/feature_guide.php"target="top";>http://promo.kde.org/3.1/feature_guide.php</a> <br>-----BEGIN PGP SIGNATURE----- <br>Version: GnuPG v1.2.1 (GNU/Linux) <br> <br>iD8DBQE+VCB31rcusafx20MRAjwlAJ9ck+qt/kUKeXhcR7ZKOt2QRTA3HQCfeBFI <br>cUt3YGVMWrHa5azgEwIGnTc= <br>=TQBU <br>-----END PGP SIGNATURE----- <br> <br> <br> <br> --------------------------------------------------- The Webtop Personal Web-based Email System http://www.yourwebtop.com
