> > > Please confirm that this is in
> > > fact the 16_1d or 16_1e release!!
Thank you thank you thank you!!! I see that 16_1e is now installed on
the server, and the world is good again.
I'm about done with extensive patches on date/time support, though I
think I won't be ready to commit them b
> > What about the server versioning issue? I see no mention of
> > REL_16_1p as being safe to use. Please confirm that this is in
> > fact the 16_1d or 16_1e release!!
> This is what is/was latest in ports after you mentioned the problem ...
> I'll check ports again over the next day or so to see
On Sat, 22 Sep 2001, Thomas Lockhart wrote:
> > Fixed ... my exclude file had a rule in it that prevented odbc from being
> > rsync'd down ... all should be downloaded now ...
>
> Great! Haven't tested it yet, but Otto is happy so I'm sure I'll be
> too...
>
> > > Server software version: REL_16_
> Fixed ... my exclude file had a rule in it that prevented odbc from being
> rsync'd down ... all should be downloaded now ...
Great! Haven't tested it yet, but Otto is happy so I'm sure I'll be
too...
> > Server software version: REL_16_1p3
> > This does *not* seem to be fresh enough. JDP reco
Thanks Marc !
I just cvsup'ed and odbc seems to be all back.
Thanks !
Best regards,
.. Otto
Otto Hirr
OLAB Inc
503.617.6595
[EMAIL PROTECTED]
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Marc
> G. Fournier
> Sent: Friday, September 21, 200
Fixed ... my exclude file had a rule in it that prevented odbc from being
rsync'd down ... all should be downloaded now ...
as for a 'sitemap', the server that all of this is on is meant to be
purelya 'mirror' of the central one on mail.postgresql.org, except there
are no accounts on the machine
> 2) I just sync'ed via cvsup at cvsup.postgresql.org and it deleted all
>under pgsql/src/interfaces/odbc/*. It also does not seem to appear
>anywhere else. What's up?
I see this too. I blew away my repository and populated it from scratch,
and still see the problem. In fact, the odbc d
On Fri, 21 Sep 2001, Thomas Lockhart wrote:
> > $ ping cvsup.postgresql.org
> > PING rs.postgresql.org: 64 byte packets
> > 64 bytes from 64.39.15.238: icmp_seq=0. time=57. ms
> > 64 bytes from 64.39.15.238: icmp_seq=1. time=70. ms
> > Perhaps there is a routing problem somewhere between you and
> $ ping cvsup.postgresql.org
> PING rs.postgresql.org: 64 byte packets
> 64 bytes from 64.39.15.238: icmp_seq=0. time=57. ms
> 64 bytes from 64.39.15.238: icmp_seq=1. time=70. ms
> Perhaps there is a routing problem somewhere between you and 64.39.15.238?
> That machine is not physically at hub (
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> Thanks for fixing it. Now of course the machine does not seem to be
> visible. That was the case yesterday too; are these planned outages, is
> it still bouncing up and down as it is configured, or is it flakey?
Looks fine from here:
$ ping cvsup.pos
Two points
1) I think that the problem with restarting at boot has occurred before.
2) I just sync'ed via cvsup at cvsup.postgresql.org and it deleted all
under pgsql/src/interfaces/odbc/*. It also does not seem to appear
anywhere else. What's up?
This is my client version:
(193)-> cvsup
just checked, and the machine has been up 14days now ... I can ssh into it
from cvs.postgresql.org, and the last cvsup connection was about 5 minutes
ago:
Sep 21 09:10:42 server1 cvsupd[50149]: +3 [EMAIL PROTECTED] (fs1.olabinc.com)
[SNAP_16_1e/16.1]
Sep 21 09:11:53 server1 cvsupd[50149]: -3 [1
> Okay, that is fixed ... for some reason, it didn't restart on last reboot,
> have to watch that one ...
Thanks for fixing it. Now of course the machine does not seem to be
visible. That was the case yesterday too; are these planned outages, is
it still bouncing up and down as it is configured,
Okay, that is fixed ... for some reason, it didn't restart on last reboot,
have to watch that one ...
On Thu, 20 Sep 2001, Thomas Lockhart wrote:
> I'm trying to update my cvs tree and am currently seeing the following:
>
> Parsing supfile "postgres.cvsup"
> Connecting to cvsup.postgresql.or
I'm trying to update my cvs tree and am currently seeing the following:
Parsing supfile "postgres.cvsup"
Connecting to cvsup.postgresql.org
Cannot connect to cvsup.postgresql.org: Connection refused
Will retry at 20:15:50
Is this expected? Should cvsup.postgresql.org be answering connection
requ
15 matches
Mail list logo
