Re: pgsql-committers list definitely wedged

From: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: pgsql-committers list definitely wedged
Date: 2000-10-16 14:44:14
Message-ID: Pine.BSF.4.21.0010161040280.4757-100000@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 16 Oct 2000, Tom Lane wrote:

> > but I see at ftp://ftp.postgresql.org/pub/dev/ that the nightly
> > snapshot hasn't updated since Monday either.
>
> As of this morning, it looks like the tar.gz files all got updated
> at 4AM EDT last night, but to judge by timestamps, the associated
> .md5 files didn't. What the heck? What script is being run by the
> cron job, anyway? ~pgsql/bin/mk-snapshot does not look like it could
> behave this way.

00 04 * * * /home/projects/pgsql/bin/mk-snapshot

And, actually, looking at the script again, it does look like it can
behave this way ... if you run a script from cron, its PATH gets set to a
'secure path', which is very limited. I set it to a specific PATH so that
/usr/local was included, but didn't realize that md5 was in /sbin ... just
added that to the path for tonights run and am running it manually now so
that its all in sync ...

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 2000-10-16 14:50:32 RE: AW: ALTER TABLE DROP COLUMN
Previous Message Bruce Momjian 2000-10-16 14:30:50 Re: bytea type