Re: pgsql-committers list definitely wedged
No, the committers list is a sendmail problem, should be fixed
momentarily, as I'm going to disable the strict domain checking on that
list ... I'll look at the snapshot thing tonight too, its using Peter's
new script(s), which appear to work great from the command line, but has a
problem when run from cron ...
On Sun, 15 Oct 2000, Tom Lane wrote:
BTW, not only is pgsql-committers wedged (still) since Monday,
but I see at ftp://ftp.postgresql.org/pub/dev/ that the nightly
snapshot hasn't updated since Monday either.Maybe related?
regards, tom lane
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
Import Notes
Reply to msg id not found: 6137.971654485@sss.pgh.pa.us
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 ...
Import Notes
Reply to msg id not found: 25745.971707080@sss.pgh.pa.us | Resolved by subject fallback