default directories

[Kyle D. Harris]

I have a few simple questions anybody but myself would know :)

What is the default directory in Redhat 9.0 that apache is in?

I do a "openssl version" and get OpenSSL 0.9.7a ... But I'd like to update it to 0.9.7c .. So where is this old 7a version located by default? It tells me the version but not sure where it is. Thanks!

[Steven E. Protter]

/etc/httpd

conf for configuration
logs for logs

htdocs for docs

This may be what you want.

SEP

[Kyle D. Harris]

I was looking through those. I was curious where it actually says "openssl 0.9.7a" and httpd-2.0.43 ...

I want to install more updated versions of both in the directory /usr/src .... How do I remove the old versions the (httpd-2.0.43 and openssl 0.9.7a) ? Or do they automatically get overlooked if there's a higher version on the system?

[Steven E. Protter]

If you installed the products from rpms simply rpm again and all binaries will be replaced. Configuration files will be left alone. This has been my experience in the past.

Red Hat is not nearly as good about this as HP-UX is with Software Distributor. Get a good backup in case I'm wrong(It happens quite often). Its those roots drilling into mhy brain.

SEP

[Kyle D. Harris]

uh oh, actually i'm installing tar.gz files. Is this the same case? Overwrites them?

[Huc_1 · Accepted solution]

Kyle,

the command
#rpm -ql openssl
will show you all that has been installed when you used normal redhat install

The command
#locate openssl
is also handy to find out where think are, or just cross check

If you are installing using tar, you could do
a
# tar -tzvf opensslXXXtar.gz > list_openssl_files

just so you are able to trouble shoot if need be after install

I would also follow SEP advise and backup before install...

and last but not least read the README and install , because often you have to taylor after install (like maybe correct path to openssl in httpd.conf etc).

If you can find it try install the openssl 9.0.7.c using the rpm version instead of tar.gz as this normaly more ease.

whatever you do enjoy.

J-P

[Steven E. Protter]

The answer to your last question depends.

You'll have to read the readme file.

Some tar distributions will overwrite. Some will make a new directory that includes the version number. Thats why the backup, especially of configuration files is critical.

I'm sure thats not a satisfactory answer, but I've had it go both ways with tar file distributions. Which is why I use depots in HP-UX and rpms in Linux.

SEP

[Balaji N]

hi,

to find out where the files for a specific package are, use

rpm -qi --filesbypkg rpmname.

to remove, rpm -e rpmname.

and since you are going to install your stuff in a new directory say, /usr/local, it doesnt matter if the old ones exist there.

i am not sure if you will be able to remove openssl so easily since there are a hell lot of dependencies on it.

-balaji

[Martin P.J. Zinser]

Actually if it is a tar.gz there is a good chance that you actually got a source distribution, which would be installed using
configure
make
make test
make install

Where to install can be set as a parameter to configure.

Also check out the type command, which will tell you where in your path a particular program lives

E.g.

zinser@bibo:/public/www/vms/fun> openssl
OpenSSL> exit
zinser@bibo:/public/www/vms/fun> type openssl
openssl is hashed (/usr/bin/openssl)
zinser@bibo:/public/www/vms/fun> ls -l /usr/bin/openssl
-rwxr-xr-x 1 root root 1128280 2003-03-25 09:29 /usr/bin/openssl

YDMV (your directories might vary ;-)

[Kyle D. Harris]

How does it work if you install a tar.gz but instead want the RPM. Once you get the RPM, what becomes of the tar.gz? Overwritten or it just sits there?

[Huc_1]

If you have installed the tar.gz and it work ! then you dont need to install the rpm version

But is you try to install rpm afterward it will probably overwrite the file distributed by tar.gz ... , and rpm may also complain that this is already installed ( I am not sure of this because I think rpm only does a check on its own "database" to find out if something is already installed).

If it work I would leave it at that!

Does it work ?

J-P

[Kyle D. Harris]

JP-
I wanted to upgrade the OpenSSL to the 0.9.7c instead of 0.9.7a to fix a bug. It game no errors when i did the make, make test, and make install.

Yet, then I did the command "openssl version" and it listed the old version of ssl (openssl-0.9.7a), so apparently it didn't work or wasnt recognized.

PS. I know what RPM is, what is SRPM?

Thanks,

Kyle

[Huc_1]

what is SRPM? --> source rpm
rpm --> binary

in the directory where you untar the tar.gz there usualy have some "readme or text file" that explains the step you need to perform to do the set up .. ?

I would first check there like

# cd to where you untar
# file *
read file that come out as text file

try and correct if you find any thing

and if all this fails try the rmp, as last resources.

keep us inform, and if you need more reply now because I will be avaiable only for an other 1/2 hour


J-P

[Kyle D. Harris]

When i try to install the RPM of this bug fix for openssl it says it conflicts with files from the tar.gz file i had installed before.

How do you weed out and remove or overwrite all these tar.gz files that are causing the conflict with the New rpm i want installed?

[Bob_Vance]

When you install from source, you ultimately do a
'make install'
to move the stuff to the final destination.

But, the *default* install directory for openssl is
"/usr/local/ssl"
.
The install locations from RPMs are probably something like
"/usr/lib/ssl"
and
"/usr/bin/openssl"
.
So, your new openssl is probably in something like
'/usr/local/ssl/bin/openssl'
.
This can be a little gritty to work thru, sometimes, especially when you start building an app that uses SSL, like SSH.

bv

[Huc_1]

Kyle,

I have just return and picking up from here

to install a binary rpm do

#rpm -Uvh 'name_of_soft'.rpm

if this does not work because it still find old openssl file you can use the -f switch in the rpm command but ! Please Beware ! this is very brutal and does just that.."force install", and so you may end up with some messy files and link.

I would consider the following senario (Please note and beware this will erase openssl from you system)
# rpm -e openssl

after that install your 0.9.7.c.rpm

#cd to the directory where you have copied your 0.9.7.c.rpm then

# rpm -Uvh openssl.0.9.7.c.rpm

hopefully the above should get rid of "old and tar mix" and install all new.

In the time between the erase and the new version install application using openssl will or may behave strangely it would be best
to stop theses if this is critical for you

This can be done by doing the following

ex; (for stopping apache)
#service httpd stop
and to start then after install of new openssl do
#service http start

after that test.

I will be busy quite late so tell us how this when !

J-P