[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Problems calling or obtaining passwords from .pgpass

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Problems calling or obtaining passwords from .pgpass
Date: Sat, 23 Nov 2013 00:15:57 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Nov 21, 2013 at 10:28:08PM +0000, Jim Busser wrote:

> This time, I put in place a 
>       .pgpass
> file of the form below, and I did not bother to uncomment the various
>       name = postgres
>       #password
> and the upgrade script was able to execute the initial portion of the 
> bootstrap, which depended on yet did not prompt me for the pw for gm-dbo
>       1) creating backup of existing database …
>       Note that this may take a substantial amount of time and disk space!
>       You may need to type in the password for gm-dbo. 

This part only runs pg_dump. It got nothing to do
with the Python part of the bootstrapper (and hence
the .conf file).

> However, after it next got to
>       Do you really want to install this database setup ?
>       Type yes or no:
> it failed (see log).

That is part of the Python code and does
not read the .pgpass file.

> It got me to observe that in
>       fixup_db-v19.conf
> the behaviour above would seem to follow from lines 75-82
>       #----------------------------------
>       [user GNUmed owner]
>       name = gm-dbo
>       password = 
>       [user postgres]
>       name = postgres
>       #password =
> where the #password seems it may need to be uncommented.

This got nothing to do with

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]