On Tue, 11 Apr 2000, Kash Ansari wrote:
>
> A customer is testing out ace on our 1200Ls and has this question:
>
> "Does ace allow alternate install locations for some of its
> packages? I went through ace to install pcp (nice!) and I
> can't recall that it does. The reason I ask is that having
> mpich installed into the main /usr tree makes it harder to
> keep track of the files, especially in the case of alternate
> builds. I'll gather together the benchmark data that we've
> been able to gather thus far."
>
> If it's yes, is it a simple edit of the installace script or something
> nasty?
>
> A choice during the installace would probably be a nice addition I would
> guess.
Fair question.
Unfortunately the PCP packages _need_ to install somethings in places
that cannot be relocated, e.g. /etc/rc.d/init.d for starters. So very
early on we decided to _not_ make the base of the PCP installations
relocatable.
However, _everything_ within PCP is referenced indirectly via the
pathnames defined in /etc/pcp.conf ... if someone _really_ wants
to move PCP pieces then they can locate the paths from /etc/pcp.conf,
move the directory and replace it by a symbolic link.
For the record, the PCP pieces are installed in
- /usr/bin ... common utilities and you can't move these, sorry
- /usr/lib ... PCP libs, and you can't move these, sorry
- /usr/include ... PCP headers, and you can't move these, sorry
- /usr/man ... PCP man pages, and you can't move these, sorry
- /var/log/pcp ... PCP logs
- /usr/share/pcp ... private PCP commands, libs, demos, odds and sods
- /var/pcp ... all of the configration stuff, agents,
|