finding files accociated with an install

[iandid...@googlemail.com]

Hi,

system = centos
lsb_release -a
LSB Version: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 5.6 (Tikanga)
Release: 5.6
Codename: Tikanga


I have inhertied a couple of servers.

Live server runs PHP version 5.1.6 build date Nov 13 2010 16:05:36
Dev server runs PHP version 5.1.6 build date May 3 2012 17:38:23


Now - I am quite happy that different build dates actually mean nothing aside from that was the date that the software was built. However, the developers assure me that this is the only difference between the two systems and so must be the issue.

So - I am requested to install the same PHP as on the live server, onto the dev server. I (and nobody I talk to) has any knowledge of the origins of these PHPs. So I have no idea if they were from an rpm, a yum install, or were built from source.

Consequently the on ly solution my coleagues and I can come up with is

* identify ALL files connected to the PHP installation on the live server
* archive their equivalents on the dev server
* copy the files from the live server to the dev server

and see if that provides the solution to the developers.

I appreciate there are inherrent risks involved but we cannot think of another way to appraoch this.

So my question/request for advice is twofold

1) how can we ascertain all the files involved in the live server's installation?

2) can anybody think of another way to do what we have been requested to do i.e. provide EXACTLY teh same PHP inmstall on the live server onto the dev server.

cheers

ian

[Andre]

I suppose you know..
rpm -q -a |grep php
if it's NOT there, it's local compile..

rpm -q -l <package found from previous cmd>
this gives the list of file in the package
André