Hi,
The have-to-subscribe list policy meant this bounced to me manually
... (hmmmm).
But, anyway, Mark/Ken does this look OK to you? It looks not quite
right wrt to detecting the "full" (-f) ps option ... but perhaps we
can think of a way to use the configure script PID still - since it
is possibly the only thing we can guarantee is running! Windows is
also a place with no init to look for.
Alternatively, since the current scheme has some serious warts, we
could bail on the current auto-detect approach and go with a fixed
ps form for each of the supported platforms.
cheers.
> ---------- Forwarded message ----------
> From: Mikel Ward <mikel@xxxxxxxxxxxxx>
> Date: Mon, Oct 4, 2010 at 2:47 PM
> Subject: [PATCH] Make ps format detection work on systems where we
> can't see root's processes.
> To: pcp@xxxxxxxxxxx
>
>
> I was trying to build PCP on a shared web host where I'm not allowed
> to see other users' processes.
>
> The configure script was trying to run "ps -ef" or "ps auxww" then
> find "init" in the output, but since init runs as root, that test
> failed with the message:
> checking for ps style... unknown
> FATAL ERROR: could not determine how to get the "all processes
> with arguments"
> format output from your ps(1).
>
> One way to consider is looking for "configure" rather than "init".
>
> Works for me anyway.
>
> Patch attached.
>
> conftest.out (output of ps) is also attached in case we need to find
> a
> different approach.
>
> Thanks
>
> Mikel
>
> configure.in | 15 ++++-----------
> 1 file changed, 4 insertions(+), 11 deletions(-)
--
Nathan
pcp-ps-no-init.patch
Description: Text Data
conftest.out
Description: Binary data
|