dopo un po di prove ho scoperto che posgresql è sempre in esecuzione
cosi ho continuato a provare e riprovare per far funzionare promogest
cosi apro gedit conf.sh <br>#!/bin/sh<br><br># Temporary directory<br>TMP=/tmp<br>CAT=/bin/cat
<br># Postgres createlang command<br>CREATELANG=/usr/bin/createlang<br># Postgres client sql<br>PSQL=/usr/bin/psql<br># Default database user<br>DB_USER=promoadmin <br># Default user password<br>DB_PASS=admin<br># user "postgres" password
<br>ADMIN_PASSWORD=<br># Database server address<br>DB_HOST=linux-suse<br># Database name<br>DB_NAME=promogest_nightly<br><br>poi apro gedit /var/lib/pgsql/data/pg_hba.conf <span class="q"><br><br># PostgreSQL Client Authentication Configuration File
<br># ===================================================<br>#<br># Refer to the "Client Authentication" section in the<br># PostgreSQL documentation for a complete description<br># of this file. A short synopsis follows.
<br>#<br># This file controls: which hosts are allowed to connect, how clients<br># are authenticated, which PostgreSQL user names they can use, which<br># databases they can access. Records take one of these forms:<br>
#
<br># local DATABASE USER METHOD [OPTION]<br> <br></span> linux-suse promogest_nightly promoadmin <a href="http://192.168.1.14/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.1.14
</a> <a href="http://255.255.255.254/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">255.255.255.254</a> trust<div><div class="ea"><span id="e_11599c2284108dfb_3">- Mostra testo tra virgolette -</span>
</div><span class="e" id="q_11599c2284108dfb_3"><br># host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
<br># hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]<br># hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]<br>#<br># (The uppercase items must be replaced by actual values.)<br>#<br># The first field is the connection type: "local" is a Unix-domain socket,
<br># "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an<br># SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.<br>#<br># DATABASE can be "all", "sameuser", "samerole", a database name, or
<br># a comma-separated list thereof.<br>#<br># USER can be "all", a user name, a group name prefixed with "+", or<br># a comma-separated list thereof. In both the DATABASE and USER fields<br># you can also write a file name prefixed with "@" to include names from
<br># a separate file.<br>#<br># CIDR-ADDRESS specifies the set of hosts the record matches.<br># It is made up of an IP address and a CIDR mask that is an integer<br># (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
<br># the number of significant bits in the mask. Alternatively, you can write<br># an IP address and netmask in separate columns to specify the set of hosts.<br>#<br># METHOD can be "trust", "reject", "md5", "crypt", "password",
<br># "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords<br># in clear text; "md5" is preferred since it sends encrypted passwords.<br>#<br>
# OPTION is the ident map or the name of the PAM service, depending on METHOD.<br>#<br># Database and user names containing spaces, commas, quotes and other special<br># characters must be quoted. Quoting one of the keywords "all", "sameuser" or
<br># "samerole" makes the name lose its special character, and just match a<br># database or username with that name.<br>#<br># This file is read on server startup and when the postmaster receives<br># a SIGHUP signal. If you edit the file on a running system, you have
<br># to SIGHUP the postmaster for the changes to take effect. You can use<br># "pg_ctl reload" to do that.<br><br># Put your actual configuration here<br># ----------------------------------<br>#<br># If you want to allow non-local connections, you need to add more
<br># "host" records. In that case you will also need to make PostgreSQL listen<br># on a non-local interface via the listen_addresses configuration parameter,<br># or via the -i or -h command line switches.<br>
#<br><br><br><br># TYPE DATABASE USER CIDR-ADDRESS METHOD<br><br># "local" is for Unix domain socket connections only<br>local all all ident sameuser<br>
# IPv4 local connections:<br>host all all <a href="http://127.0.0.1/32" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">127.0.0.1/32</a> ident sameuser<br># IPv6 local connections:
<br>host all all ::1/128 ident sameuser
<br><br></span></div><span class="q"> # PostgreSQL Client Authentication Configuration File<br># ===================================================<br>#<br># Refer to the "Client Authentication" section in the
<br># PostgreSQL documentation for a complete description
<br># of this file. A short synopsis follows.<br>#<br># This file controls: which hosts are allowed to connect, how clients<br># are authenticated, which PostgreSQL user names they can use, which<br># databases they can access. Records take one of these forms:
<br>#<br># local DATABASE USER METHOD [OPTION]<br> <br></span> linux-suse promogest_nightly promoadmin <a href="http://192.168.1.14/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.1.14
</a> <a href="http://255.255.255.254/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">255.255.255.254</a> trust<div><div class="ea"><span id="e_11599c2284108dfb_6">- Mostra testo tra virgolette -</span>
</div><span class="e" id="q_11599c2284108dfb_6"><br># host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
<br># hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]<br># hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]<br>#<br># (The uppercase items must be replaced by actual values.)<br>#<br># The first field is the connection type: "local" is a Unix-domain socket,
<br># "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an<br># SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.<br>#<br># DATABASE can be "all", "sameuser", "samerole", a database name, or
<br># a comma-separated list thereof.<br>#<br># USER can be "all", a user name, a group name prefixed with "+", or<br># a comma-separated list thereof. In both the DATABASE and USER fields<br># you can also write a file name prefixed with "@" to include names from
<br># a separate file.<br>#<br># CIDR-ADDRESS specifies the set of hosts the record matches.<br># It is made up of an IP address and a CIDR mask that is an integer<br># (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
<br># the number of significant bits in the mask. Alternatively, you can write<br># an IP address and netmask in separate columns to specify the set of hosts.<br>#<br># METHOD can be "trust", "reject", "md5", "crypt", "password",
<br># "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords<br># in clear text; "md5" is preferred since it sends encrypted passwords.<br>#<br>
# OPTION is the ident map or the name of the PAM service, depending on METHOD.<br>#<br># Database and user names containing spaces, commas, quotes and other special<br># characters must be quoted. Quoting one of the keywords "all", "sameuser" or
<br># "samerole" makes the name lose its special character, and just match a<br># database or username with that name.<br>#<br># This file is read on server startup and when the postmaster receives<br># a SIGHUP signal. If you edit the file on a running system, you have
<br># to SIGHUP the postmaster for the changes to take effect. You can use<br># "pg_ctl reload" to do that.<br><br># Put your actual configuration here<br># ----------------------------------<br>#<br># If you want to allow non-local connections, you need to add more
<br># "host" records. In that case you will also need to make PostgreSQL listen<br># on a non-local interface via the listen_addresses configuration parameter,<br># or via the -i or -h command line switches.<br>
#<br><br><br><br># TYPE DATABASE USER CIDR-ADDRESS METHOD<br><br># "local" is for Unix domain socket connections only<br>local all all ident sameuser<br>
# IPv4 local connections:<br>host all all <a href="http://127.0.0.1/32" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">127.0.0.1/32</a> ident sameuser<br># IPv6 local connections:
<br>host all all ::1/128 ident sameuser
<br><br></span></div><span class="q"> # PostgreSQL Client Authentication Configuration File<br># ===================================================<br>#<br># Refer to the "Client Authentication" section in the
<br># PostgreSQL documentation for a complete description
<br># of this file. A short synopsis follows.<br>#<br># This file controls: which hosts are allowed to connect, how clients<br># are authenticated, which PostgreSQL user names they can use, which<br># databases they can access. Records take one of these forms:
<br>#<br># local DATABASE USER METHOD [OPTION]<br> <br></span> linux-suse promogest_nightly promoadmin <a href="http://192.168.1.14/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.1.14
</a> <a href="http://255.255.255.254/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">255.255.255.254</a> trust<br>segue ----><br><br><div><span class="gmail_quote">2007/10/13, angelo morrone <
<a href="mailto:angelomorr@gmail.com">angelomorr@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">dopo un po di prove ho scoperto che posgresql è sempre in esecuzione cosi ho continuato a provare e riprovare per far funzionare promogest cosi apro gedit
conf.sh <br>#!/bin/sh<br><br># Temporary directory<br>TMP=/tmp<br>CAT=/bin/cat
<br># Postgres createlang command<br>CREATELANG=/usr/bin/createlang<br># Postgres client sql<br>PSQL=/usr/bin/psql<br># Default database user<br>DB_USER=promoadmin <br># Default user password<br>DB_PASS=admin<br># user "postgres" password
<br>ADMIN_PASSWORD=<br># Database server address<br>DB_HOST=linux-suse<br># Database name<br>DB_NAME=promogest_nightly<br><br>poi apro gedit /var/lib/pgsql/data/pg_hba.conf <span class="q"><br><br># PostgreSQL Client Authentication Configuration File
<br># ===================================================<br>#<br># Refer to the "Client Authentication" section in the<br># PostgreSQL documentation for a complete description<br># of this file. A short synopsis follows.
<br>#<br># This file controls: which hosts are allowed to connect, how clients<br># are authenticated, which PostgreSQL user names they can use, which<br># databases they can access. Records take one of these forms:<br>
#
<br># local DATABASE USER METHOD [OPTION]<br> <br></span> linux-suse promogest_nightly promoadmin <a href="http://192.168.1.14" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.1.14
</a> <a href="http://255.255.255.254" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">255.255.255.254</a> trust<div><span class="e" id="q_11599c2284108dfb_3"><br># host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
<br># hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]<br># hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]<br>#<br># (The uppercase items must be replaced by actual values.)<br>#<br># The first field is the connection type: "local" is a Unix-domain socket,
<br># "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an<br># SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.<br>#<br># DATABASE can be "all", "sameuser", "samerole", a database name, or
<br># a comma-separated list thereof.<br>#<br># USER can be "all", a user name, a group name prefixed with "+", or<br># a comma-separated list thereof. In both the DATABASE and USER fields<br># you can also write a file name prefixed with "@" to include names from
<br># a separate file.<br>#<br># CIDR-ADDRESS specifies the set of hosts the record matches.<br># It is made up of an IP address and a CIDR mask that is an integer<br># (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
<br># the number of significant bits in the mask. Alternatively, you can write<br># an IP address and netmask in separate columns to specify the set of hosts.<br>#<br># METHOD can be "trust", "reject", "md5", "crypt", "password",
<br># "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords<br># in clear text; "md5" is preferred since it sends encrypted passwords.<br>#<br>
# OPTION is the ident map or the name of the PAM service, depending on METHOD.<br>#<br># Database and user names containing spaces, commas, quotes and other special<br># characters must be quoted. Quoting one of the keywords "all", "sameuser" or
<br># "samerole" makes the name lose its special character, and just match a<br># database or username with that name.<br>#<br># This file is read on server startup and when the postmaster receives<br># a SIGHUP signal. If you edit the file on a running system, you have
<br># to SIGHUP the postmaster for the changes to take effect. You can use<br># "pg_ctl reload" to do that.<br><br># Put your actual configuration here<br># ----------------------------------<br>#<br># If you want to allow non-local connections, you need to add more
<br># "host" records. In that case you will also need to make PostgreSQL listen<br># on a non-local interface via the listen_addresses configuration parameter,<br># or via the -i or -h command line switches.<br>
#<br><br><br><br># TYPE DATABASE USER CIDR-ADDRESS METHOD<br><br># "local" is for Unix domain socket connections only<br>local all all ident sameuser<br>
# IPv4 local connections:<br>host all all <a href="http://127.0.0.1/32" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">127.0.0.1/32</a> ident sameuser<br># IPv6 local connections:
<br>host all all ::1/128 ident sameuser
<br><br></span></div><span class="q"> # PostgreSQL Client Authentication Configuration File<br># ===================================================<br>#<br># Refer to the "Client Authentication" section in the
<br># PostgreSQL documentation for a complete description
<br># of this file. A short synopsis follows.<br>#<br># This file controls: which hosts are allowed to connect, how clients<br># are authenticated, which PostgreSQL user names they can use, which<br># databases they can access. Records take one of these forms:
<br>#<br># local DATABASE USER METHOD [OPTION]<br> <br></span> linux-suse promogest_nightly promoadmin <a href="http://192.168.1.14" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.1.14
</a> <a href="http://255.255.255.254" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">255.255.255.254</a> trust<div><span class="e" id="q_11599c2284108dfb_6"><br># host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
<br># hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]<br># hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]<br>#<br># (The uppercase items must be replaced by actual values.)<br>#<br># The first field is the connection type: "local" is a Unix-domain socket,
<br># "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an<br># SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.<br>#<br># DATABASE can be "all", "sameuser", "samerole", a database name, or
<br># a comma-separated list thereof.<br>#<br># USER can be "all", a user name, a group name prefixed with "+", or<br># a comma-separated list thereof. In both the DATABASE and USER fields<br># you can also write a file name prefixed with "@" to include names from
<br># a separate file.<br>#<br># CIDR-ADDRESS specifies the set of hosts the record matches.<br># It is made up of an IP address and a CIDR mask that is an integer<br># (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
<br># the number of significant bits in the mask. Alternatively, you can write<br># an IP address and netmask in separate columns to specify the set of hosts.<br>#<br># METHOD can be "trust", "reject", "md5", "crypt", "password",
<br># "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords<br># in clear text; "md5" is preferred since it sends encrypted passwords.<br>#<br>
# OPTION is the ident map or the name of the PAM service, depending on METHOD.<br>#<br># Database and user names containing spaces, commas, quotes and other special<br># characters must be quoted. Quoting one of the keywords "all", "sameuser" or
<br># "samerole" makes the name lose its special character, and just match a<br># database or username with that name.<br>#<br># This file is read on server startup and when the postmaster receives<br># a SIGHUP signal. If you edit the file on a running system, you have
<br># to SIGHUP the postmaster for the changes to take effect. You can use<br># "pg_ctl reload" to do that.<br><br># Put your actual configuration here<br># ----------------------------------<br>#<br># If you want to allow non-local connections, you need to add more
<br># "host" records. In that case you will also need to make PostgreSQL listen<br># on a non-local interface via the listen_addresses configuration parameter,<br># or via the -i or -h command line switches.<br>
#<br><br><br><br># TYPE DATABASE USER CIDR-ADDRESS METHOD<br><br># "local" is for Unix domain socket connections only<br>local all all ident sameuser<br>
# IPv4 local connections:<br>host all all <a href="http://127.0.0.1/32" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">127.0.0.1/32</a> ident sameuser<br># IPv6 local connections:
<br>host all all ::1/128 ident sameuser
<br><br></span></div><span class="q"> # PostgreSQL Client Authentication Configuration File<br># ===================================================<br>#<br># Refer to the "Client Authentication" section in the
<br># PostgreSQL documentation for a complete description
<br># of this file. A short synopsis follows.<br>#<br># This file controls: which hosts are allowed to connect, how clients<br># are authenticated, which PostgreSQL user names they can use, which<br># databases they can access. Records take one of these forms:
<br>#<br># local DATABASE USER METHOD [OPTION]<br> <br></span> linux-suse promogest_nightly promoadmin <a href="http://192.168.1.14" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.1.14
</a> <a href="http://255.255.255.254" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">255.255.255.254</a> trust<div><span class="e" id="q_11599c2284108dfb_9"><br># host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
<br># hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]<br># hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]<br>#<br># (The uppercase items must be replaced by actual values.)<br>#<br># The first field is the connection type: "local" is a Unix-domain socket,
<br># "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an<br># SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.<br>#<br># DATABASE can be "all", "sameuser", "samerole", a database name, or
<br># a comma-separated list thereof.<br>#<br># USER can be "all", a user name, a group name prefixed with "+", or<br># a comma-separated list thereof. In both the DATABASE and USER fields<br># you can also write a file name prefixed with "@" to include names from
<br># a separate file.<br>#<br># CIDR-ADDRESS specifies the set of hosts the record matches.<br># It is made up of an IP address and a CIDR mask that is an integer<br># (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
<br># the number of significant bits in the mask. Alternatively, you can write<br># an IP address and netmask in separate columns to specify the set of hosts.<br>#<br># METHOD can be "trust", "reject", "md5", "crypt", "password",
<br># "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords<br># in clear text; "md5" is preferred since it sends encrypted passwords.<br>#<br>
# OPTION is the ident map or the name of the PAM service, depending on METHOD.<br>#<br># Database and user names containing spaces, commas, quotes and other special<br># characters must be quoted. Quoting one of the keywords "all", "sameuser" or
<br># "samerole" makes the name lose its special character, and just match a<br># database or username with that name.<br>#<br># This file is read on server startup and when the postmaster receives<br># a SIGHUP signal. If you edit the file on a running system, you have
<br># to SIGHUP the postmaster for the changes to take effect. You can use<br># "pg_ctl reload" to do that.<br><br># Put your actual configuration here<br># ----------------------------------<br>#<br># If you want to allow non-local connections, you need to add more
<br># "host" records. In that case you will also need to make PostgreSQL listen<br># on a non-local interface via the listen_addresses configuration parameter,<br># or via the -i or -h command line switches.<br>
#<br><br><br><br># TYPE DATABASE USER CIDR-ADDRESS METHOD<br><br># "local" is for Unix domain socket connections only<br>local all all ident sameuser<br>
# IPv4 local connections:<br>host all all <a href="http://127.0.0.1/32" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">127.0.0.1/32</a> ident sameuser<br># IPv6 local connections:
<br>host all all ::1/128 ident sameuser
<br><br></span></div>avvio su postgres /install_db.sh <br><br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione<br>
e che accetti connessioni TCP/IP sulla porta 5432?
<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione<br> e che accetti connessioni TCP/IP sulla porta 5432?
<br>createlang: impossibile connettersi al database promogest_nightly: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br>psql: impossibile connettersi al server: Connessione rifiutata<br> Controllare che il server all'indirizzo "linux-suse" sia in funzione
<br> e che accetti connessioni TCP/IP sulla porta 5432?<br><br><br>e poi lancio ./install<br><div><span class="gmail_quote">Il 12/10/07, <b class="gmail_sendername">angelo morrone</b> <<a href="mailto:angelomorr@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
angelomorr@gmail.com</a>> ha scritto:</span><div><span class="e" id="q_11599c2284108dfb_11"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Stranissimo ho provato #/etc/init.d/postgresql stop, start ma la cosa strana che quando #/etc/init.d/postgresql status mi dice che è in esecuzione boooo. con #/etc/init.d/postgresql stop Shutting down PostgreSQLserver stopped
<br> done<span><br><br> /etc/init.d/postgresql status<br></span>Checking for PostgreSQL: running<br>
strano si comporta cosi perchè ho aggiornato sia il kernel che il server x?
<br>forse sono installati i pacchetti sbagliati?<br>aiutooooooooo!!!!<br><br><div><span class="gmail_quote">Il 12/10/07, <b class="gmail_sendername">Francesco Steno</b> <<a href="mailto:overdrive@linux.it" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
overdrive@linux.it
</a>> ha scritto:</span><div><span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Il giorno 11/ott/07, alle ore 22:45, angelo morrone ha scritto:
<br><br>> Nuovo problema dopo inserito la riga linux-suse promogest_db<br>> promoadmin<br>> <a href="http://192.168.1.14" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">192.168.1.14</a> <a href="http://255.255.255.255" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
255.255.255.255</a> trust in /var/lib/pgsql/data/
<br>> pg_hba.conf non<br>> mi parte più /etc/init.d/postgresql start<br>> Starting PostgreSQLcould not start server<br>> provo cosi local promogest_db promoadmin <a href="http://192.168.1.14" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
192.168.1.14</a><br>
> <a href="http://255.255.255.255" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">255.255.255.255</a> trust<br>> e mi dice /etc/init.d/postgresql start<br>> Starting PostgreSQLpg_ctl: another server may be running;
<br>> trying to start server anyway<br>> pg_ctl: could not start server
<br>> Examine the log output.<br>> f<br>> ailed<br>> Come si fò?<br><br>vuol dire che devi prima fermare il server che sta girando, e poi lo
<br>fai ripartire....<br><br>#/etc/init.d/postgresql stop (ferma il server)<br>#/etc/init.d/postgresql start (fa partire il server)<br>#/etc/init.d/postgresql status (ti dice se il server e' in<br>esecuzione, oppure se e' fermo)
<br>#/etc/init.d/postgresql restart (nel caso sia in esecuzione, lo ferma<br>e lo fa ripartire)<br><br>Prova cosi e fammi sapere<br><br><br>Francesco Steno aka "oVERDRIVE"<br><br><br>--<br><br>-=-=-=-=-=-=-=-=-=-=-=-=-=-generated by /dev/over-=-=-=-=-=-=-=-=-=-=
<br> oVERDRIVE<br><<a href="mailto:overdrive@OpenGeeks.it" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">overdrive@OpenGeeks.it</a>><<a href="mailto:overdrive@BitchX.it" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
overdrive@BitchX.it</a>><<a href="mailto:overdrive@Linux.it" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
overdrive@Linux.it</a>><br> GnuPG Public Key: <a href="http://cb.linux.it/lug/key/overdrive.asc" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://cb.linux.it/lug/key/overdrive.asc
</a><br> Key Fingerprint: 146A E13D 9E68 3B96 40FB 11F5 9A10 2D1F 3973 C203
<br><br><br><br><br>--<br>Mailing list info: <a href="http://lists.linux.it/listinfo/lugcb" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.linux.it/listinfo/lugcb</a><br></blockquote>
</span></div></div><br>
</blockquote></span></div></div><br>
</blockquote></div><br>