From: | Oleg Lebedev <olebedev(at)waterford(dot)org> |
---|---|
To: | Postgres SQL Mailing List <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Connection authentication |
Date: | 2002-04-26 20:01:19 |
Message-ID: | 3CC9B20F.6511C8D3@waterford.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
I checked PGUSER/PGPASSWORD settings for the root and the user which runs the
cron job and they seem to be fine. However, I get the following messages in
the root mail:
Connection to database 'webspec' failed.
fe_sendauth: no password supplied.
Any ideas?
thanks,
Oleg
Bruce Momjian wrote:
> 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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2002-04-26 20:42:53 | Re: union query format |
Previous Message | Josh Berkus | 2002-04-26 19:38:44 | Wierd query behaviour |