problem with last change to _get_pids_by_name() in pcp.env

Ken McDonell <[email protected]>
Newsgroups gmane.comp.sysutils.pcp
Message-ID <[email protected]>
Commit 63ce703 forces matching to the full pathname of the binary (not a 
bad idea in principle, and motivated by a real issue) ... but the 
implementation fails (spectacularly) when the

(a) the shell running _get_pids_by_name() has a different $PATH than the 
shell that was used to launch the binary in question, so which(1) and 
exec(2) may refer to different binaries, and/or
(b) the binary in question was launched via a symbolic link.

Specifically pmlogger (on at least some distros) lives in /usr/bin and 
as a symlink in $PCP_BINADM_DIR ... I have a bunch of QA failures from 
the resulting mismatch.

I don't have a fix as yet, but this is a heads up for others pending 
resolution.

_______________________________________________
pcp mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/pcp
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.