> > Connection to database 'mibsedatos' failed. > >ERROR: connectDB() - connect() failed: ConexiCn rehusada > >Is the postmaster running (with -i) at 'localhost' and > >accepting connections on TCP/IP port '5432'? > > > > With psql no problem but the problem comes out with > >mpsql and pgaccess. > >It sounds as though mpsql is trying to connect to the socket in >its old location. make a symbolic link: > > ln -s /var/run/postgresql/.s.PGSQL.5432 /tmp/.s.PGSQL.5432 > >(Why is mpsql doing this? Is it compiled with a static library?) > >pgaccess without mpsql works fine. > >-- >Oliver Elphick [EMAIL PROTECTED] >Isle of Wight http://www.lfix.co.uk/oliver >PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47 >GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C > ======================================== > "Give to him that asketh thee, and from him that would > borrow of thee turn not away." > Matthew 5:42 --------------------------------------------------------------------------------- ************************************************************ --------------------------------------------------------------------------------- > >Leave the "hostname" and just about everything blank for the connection >configuration. That should force the use of UNIX sockets rather than >TCP/IP sockets. > >See /etc/postgresql/pg_hba.conf for changing security >configuration, and /etc/postgresql/postmaster.init for options for the >postmaster (like listening for TCP/IP connections). > > >-- >Eric G. Miller <egm2@jps.net>
Thanks Very Much to both of you. It works now. I 've just left everything blank except the 'database name' and works fine with pgaccess but no with mpsql, because mpsql doesn't let me keep anything blank. Cheers. _______________________________________________________________ Do You Yahoo!? Consiga gratis su dirección @yahoo.es en http://correo.yahoo.es