> On 11/04/2008, at 12:03 AM, Nathan Scott wrote:
>>
>> - the platform-specific part could be replaced by a
>> pcp.conf variable $PCP_PLATFORM_PATHS, which sysadmins
>> can add to if they have "special" PATH needs for custom
>> PMDAs, like me!
>
> Sounds OK. IMHO PCP should (by default) only look in the minimum set
> of paths ... /usr/bin and friends
Its occurred to me since we last discussed this why it is as it is - the
open source PCP build and runtime has a heavy dependency on many
GNU tools (like gmake, esp). These are often not on the usual PATH,
and are squirrelled away someplace special - except on Linux and
Mac OS X and Cygwin, where they are the default tools.
For those platforms, and now that we changed the configure AWK test,
which looks in all manner of places, I think we can safely remove some
of the PATH extensions, for those platforms.
>> /usr/bsd - FreeBSD
>> /usr/etc - IRIX
>> /usr/bin/X11 - UNIX platforms
>> /usr/local/bin - UNIX platforms
>> /opt/sfw/bin - ?
>
> Sun Freeware
>
Taa.
>>
>> /usr/ccs/bin - ?
>
>
> solaris BSD compat subsystem?
>
Yep - google found it, and also mail saying its been deprecated for awhile
(in favour of /usr/bin, etc).
>>
>> /cygdrive/c/WINDOWS/system32 - Windows/Cygwin
>> /usr/contrib/bin - ?
>> /opt/local/bin - Mac OS X
>
> MacPorts - There is the fink project, which sold we /sw/bin
>
I think I'm finally convinced we can drop these two. :)
The one remaining oddity I see is that "/etc" is part of the default PCP
path ... anyone know why that might be? Was that a need from IRIX?
cheers.
--
Nathan
|