BTW, the init file has this:
# chkconfig: - 85 15
I would modestly suggest changing this to something like 81 19. The
reason - these are the same settinga as httpd, and I normally want Pg
started up before the web server and shut down after the web server.
andrew
Andrew Dunstan wrote:
Seems
Seems to be OK. See below.
BTW, for those interested, following up a note from Joe Conway I
discovered yesterday the Right Way (tm) to build RPMs (nothing Pg
specific in this). Basically, you set up some rpm macros like this in
~/.rpmmacros:
%_topdir%(echo ${HOME}/rpm)
%_tmppath
On Tuesday 05 August 2003 08:14, Andrew Dunstan wrote:
> Will check later today.
When you do, let me know, so that I can post them.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
---(end of broadcast)---
TIP
Mark Cave-Ayland said:
> Hi there,
>
> I have a RedHat 7.3 machine that can build the 7.3.4 RPMs if required -
> it only contains RPMs from the vanilla CD or from updates.redhat.com.
> I've just done a test build and everything seems OK except that the C
> compiler is passed the -mcpu=i686 flag -
Hi there,
I have a RedHat 7.3 machine that can build the 7.3.4 RPMs if required -
it only contains RPMs from the vanilla CD or from updates.redhat.com.
I've just done a test build and everything seems OK except that the C
compiler is passed the -mcpu=i686 flag - I'm guessing I need to somehow
chan
stan'; 'Lamar Owen'; 'Postgresql Hackers'
> Subject: Re: [HACKERS] problem with RH7.3 Pg7.3.4 binaries
>
>
>
> Mark Cave-Ayland said:
> > Hi there,
> >
> > I have a RedHat 7.3 machine that can build the 7.3.4 RPMs
> if required
> > -
sender. You
> should not copy it or use it for any purpose nor disclose or distribute
> its contents to any other person.
>
> > -----Original Message-
> > From: Magnus Naeslund(w) [mailto:[EMAIL PROTECTED]
> > Sent: 05 August 2003 10:59
> > To: Mark Cave-Ayland
>
On Monday 04 August 2003 13:57, Joe Conway wrote:
> I just checked, and the RHAS that I built the RPMs on is pretty close to
> original, other than kernel and some driver updates. I'll let you decide
> whether to pull them or not, but they don't meet your "fully-updated
> install" criterion.
Hmmm.
Joe Conway wrote:
Lamar Owen wrote:
I've thus far used the definition that it is a fully-updated install,
using the OS vendor's update packages that are dependencies of
PostgreSQL. Updating to, say, a later KDE, or GNUcash, or whatnot is
OK. But core libraries that PostgreSQL uses need to stay
I agree with the definition of "vanilla install" below.
I can't use the machine I was upgrading to build, unfortunately. Its a
production machine I am prepping, (and is missing stuff the build
process needs even if I wanted to monkey with it), which is precisely
why I wanted to install from RPM
Lamar Owen wrote:
On Monday 04 August 2003 13:00, Joe Conway wrote:
I don't think so -- the server I built those on is very much vanilla
RHAS. But then this raises a question in my mind -- is vanilla a fully
updated vanilla or "off the original CDs" vanilla?
I've thus far used the definition that
On Monday 04 August 2003 13:00, Joe Conway wrote:
> I don't think so -- the server I built those on is very much vanilla
> RHAS. But then this raises a question in my mind -- is vanilla a fully
> updated vanilla or "off the original CDs" vanilla?
I've thus far used the definition that it is a full
Lamar Owen wrote:
Joe, the RHAS binaries won't have this problem, right?
I don't think so -- the server I built those on is very much vanilla
RHAS. But then this raises a question in my mind -- is vanilla a fully
updated vanilla or "off the original CDs" vanilla?
To prevent this in the future, I
On Monday 04 August 2003 11:53, Joe Conway wrote:
> Andrew Dunstan wrote:
> > I know building RPMs can be a major pain, but ISTM that builds should be
> > published that don't break on vanilla installations. I'm prepared to
> > help with fixing this if necessary. For now I've upgraded to 7.3.3 (the
Andrew Dunstan wrote:
I know building RPMs can be a major pain, but ISTM that builds should be
published that don't break on vanilla installations. I'm prepared to
help with fixing this if necessary. For now I've upgraded to 7.3.3 (the
RPMs for this don't suffer the same problem on RH7.3).
Sorr
(Not sure if hackers is the right place for this, but I'm not subscribed
to all the lists!)
The distributed 7.3.4 RPMs for RH 7.3 require libcrypto.so.3 and
libssl.so.3, but there does not appear to be any official RH update for
7.3 containing these libs. I do have the latest RH openssl updates
16 matches
Mail list logo
