Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (Postfix) with ESMTP id ABACE475945 for ; Thu, 25 Apr 2002 10:43:33 -0400 (EDT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g3PEhSb12314; Thu, 25 Apr 2002 10:43:28 -0400 (EDT) From: Bruce Momjian Message-Id: <200204251443.g3PEhSb12314@candle.pha.pa.us> Subject: Re: Connection authentication In-Reply-To: <3CC7085C.75D70C72@waterford.org> To: Oleg Lebedev Date: Thu, 25 Apr 2002 10:43:28 -0400 (EDT) Cc: Postgres SQL Mailing List X-Mailer: ELM [version 2.4ME+ PL97 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200204/306 X-Sequence-Number: 7570 Oleg Lebedev wrote: > Hello, > I have a problem running a CRON job that vacuums and backs up my > database when authentication type is set to 'password' in pg_hba.conf > file. I used to have 'trust'ed settings before and everything was > working fine. Now I switched to password authentication type, but how > would a cron script send the password when prompted. I tried to set up > PGUSER and PGPASSWORD env. vars, but psql still prompts for the > password. > Any ideas? > I am using PostgreSQL 7.1.3 on Red Hat Linux 7.1. > thanks, PGUSER/PGPASSWORD certainly should work. Did you export them properly? The only other idea I have is upgrading to 7.2 where on Linux you can use ident on local connections. It uses socket authentication and will not require a password and you don't have to run ident. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026