Re: [PATCH v3] cpupower: Make help command available for custom install dir

[Shuah Khan <skhan@linuxfoundation.org>]

On 6/28/24 05:30, Roman Storozhenko wrote:
> On Thu, Jun 27, 2024 at 7:33 PM Shuah Khan <skhan@linuxfoundation.org> wrote:
>>
>> On 6/27/24 01:49, Roman Storozhenko wrote:
>>> When the 'cpupower' utility installed in the custom dir, it fails to
>>> render appropriate help info for a particular subcommand:
>>> $ LD_LIBRARY_PATH=lib64/ bin/cpupower help monitor
>>> with error message like 'No manual entry for cpupower-monitor.1'
>>> The issue is that under the hood it calls 'exec' function with
>>> the following args: 'man cpupower-monitor.1'. In turn, 'man' search
>>> path is defined in '/etc/manpath.config'. Of course it contains only
>>> standard system man paths.
>>> Make subcommands help available for a user by setting up 'MANPATH'
>>> environment variable to the custom installation man pages dir. That
>>> variable value will be prepended to the man pages standard search paths
>>> as described in 'SEARCH PATH' section of MANPATH(5).
>>
>> What I am asking you is what happens when you set the MANPATH before
>> running the command?
> 
> It adds the custom search path to the beginning of the MANPATH variable.
> I tested this case. All works as expected.
> 

Let's try again. What happens if you run the command with MANPATH set and
exported and then run the command. Can you send the output?

thanks,
-- Shuah