Run-time path separator and drive specification, for Windows.
On Windows we need to operate within a native (cmd.exe) shell
(for PCP commands) and POSIX shell environment (start scripts,
PMDA Install/Remove, etc, etc...). To assist with this, and
with future relocatable installation on Windows, introduce a
pmconfig tool which wraps pmGetConfig(3), used by pcp.env, and
PCP_DIR environment variable specifying PCP installation root.
Allow _get_pids_by_name (pcp.env) to work on Windows, where we
have to cope with .exe-suffixed commands appearing in ps text.
Add in Windows-specific code to pmcd to deal with daemonising
the process. These changes get us to a functional namespace
Rebuild, pcp start script ("start", "status" works ... "stop"
not so much), and fully functional kernel+pmcd DSO agents.
Run-time path separator and drive specification, for Windows.
On Windows we need to operate within a native (cmd.exe) shell
(for PCP commands) and POSIX shell environment (start scripts,
PMDA Install/Remove, etc, etc...). To assist with this, and
with future relocatable installation on Windows, introduce a
pmconfig tool which wraps pmGetConfig(3), used by pcp.env, and
PCP_DIR environment variable specifying PCP installation root.
Allow _get_pids_by_name (pcp.env) to work on Windows, where we
have to cope with .exe-suffixed commands appearing in ps text.
Add in Windows-specific code to pmcd to deal with daemonising
the process. These changes get us to a functional namespace
Rebuild, pcp start script ("start", "status" works ... "stop"
not so much), and fully functional kernel+pmcd DSO agents.