Re: configuracion

From: "jose landaeta" <jlandaeta(at)mpd(dot)gov(dot)ve>
To: "Wdiaz" <wdiaz(at)unipamplona(dot)edu(dot)co>
Cc: <pgsql-es-ayuda(at)postgresql(dot)org>
Subject: Re: configuracion
Date: 2006-09-13 19:12:02
Message-ID: 001601c6d768$7f23a190$1de0020a@elandaeta
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-es-ayuda

muchisimas gracias por tu ayuda, tratare de hacer lo indicado y cuando tenga
resultados te mando una respuesta, de todo corazon muchas gracias
----- Original Message -----
From: "Wdiaz" <wdiaz(at)unipamplona(dot)edu(dot)co>
To: <jlandaeta(at)mpd(dot)gov(dot)ve>
Cc: <pgsql-es-ayuda(at)postgresql(dot)org>
Sent: Thursday, September 07, 2006 3:36 PM
Subject: Re: [pgsql-es-ayuda] configuracion

> Debes buscar la ubicación del archcivo pg_hba.con (find / -iname
> "pg_hba.conf") y hacer un registro de acceso para la maquina donde
> tienes instalado el pgAdmin te envio el ejemplo del que yo uso en Linux
> RedHat ES 4.
>
> el archivo en mi servidor se encuentra en: /var/lib/pgsql/data/pg_hba.conf
>
> su contenido es:
>
>
> # PostgreSQL Client Authentication Configuration File
> # ===================================================
> #
> # Refer to the PostgreSQL Administrator's Guide, chapter "Client
> # Authentication" for a complete description. A short synopsis
> # follows.
> #
> # This file controls: which hosts are allowed to connect, how clients
> # are authenticated, which PostgreSQL user names they can use, which
> # databases they can access. Records take one of these forms:
> #
> # local DATABASE USER METHOD [OPTION]
> # host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
> # hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
> # hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
> #
> # (The uppercase items must be replaced by actual values.)
> #
> # The first field is the connection type: "local" is a Unix-domain socket,
> # "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an
> # SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.
> #
> # DATABASE can be "all", "sameuser", "samerole", a database name, or
> # a comma-separated list thereof.
> #
> # USER can be "all", a user name, a group name prefixed with "+", or
> # a comma-separated list thereof. In both the DATABASE and USER fields
> # you can also write a file name prefixed with "@" to include names from
> # a separate file.
> #
> # CIDR-ADDRESS specifies the set of hosts the record matches.
> # It is made up of an IP address and a CIDR mask that is an integer
> # (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
> # the number of significant bits in the mask. Alternatively, you can
write
> # an IP address and netmask in separate columns to specify the set of
hosts.
> #
> # METHOD can be "trust", "reject", "md5", "crypt", "password",
> # "krb5", "ident", or "pam". Note that "password" sends passwords
> # in clear text; "md5" is preferred since it sends encrypted passwords.
> #
> # OPTION is the ident map or the name of the PAM service, depending on
> METHOD.
> #
> # Database and user names containing spaces, commas, quotes and other
> special
> # characters must be quoted. Quoting one of the keywords "all",
> "sameuser" or
> # "samerole" makes the name lose its special character, and just match a
> # database or username with that name.
> #
> # This file is read on server startup and when the postmaster receives
> # a SIGHUP signal. If you edit the file on a running system, you have
> # to SIGHUP the postmaster for the changes to take effect. You can use
> # "pg_ctl reload" to do that.
>
> # Put your actual configuration here
> # ----------------------------------
> #
> # If you want to allow non-local connections, you need to add more
> # "host" records. In that case you will also need to make PostgreSQL
listen
> # on a non-local interface via the listen_addresses configuration
parameter,
> # or via the -i or -h command line switches.
> #
>
>
>
> # TYPE DATABASE USER CIDR-ADDRESS METHOD
>
> # "local" is for Unix domain socket connections only
> local all all ident sameuser
> # IPv4 local connections:
> host all all 127.0.0.1/32 ident sameuser
> # IPv6 local connections:
> host all all ::1/128 ident sameuser
> host all all 172.29.108.145 255.255.255.255 trust
> host ads all 172.29.108.200 255.255.255.255 trust
> host all all 172.29.108.76 255.255.255.255 trust
> host fondo all 172.29.108.254 255.255.255.255 trust
> host all all 172.29.108.79 255.255.255.255 trust
>
>
> Yo configuro el postgres a traves de la herramienta webmin.
>
>
> Espero le pueda servir
>
> jose enrique landaeta escribió:
> > ya he tratado por todos los medios de configurar pgadmin3 para trabajar
> > con postgresql 7.4 en debian etch, pero no se me conecta al servidor, si
> > trabajo por consola con el postgres sale perfecto pero cuando trato de
> > trabajarlo con pgadmin3 me sale un error de que no consigue el archivo
> > pg_hba.conf, que puedo hacer para solucionarlo
> >
> >
> > ---------------------------(fin del mensaje)---------------------------
> > TIP 1: para suscribirte y desuscribirte, visita
http://archives.postgresql.org/pgsql-es-ayuda
> >
> >
> >
>
>
> --
> Cordialmente
>
> William Diaz Pabón
> Coordinador Técnico de Desarrollo
> Vicerrectoría de Gestión y Desarrollo Tecnológico
> Universidad de Pamplona
>

In response to

Browse pgsql-es-ayuda by date

  From Date Subject
Next Message Edwin Quijada 2006-09-13 19:38:01 Re: [OT]Java o J2EE
Previous Message Emiliano Pereyra 2006-09-13 18:46:34 Problemas al crear un Tablespace en WinXP