From: Shuah Khan <skhan@linuxfoundation.org>
To: Roman Storozhenko <romeusmeister@gmail.com>,
Thomas Renninger <trenn@suse.com>, Shuah Khan <shuah@kernel.org>
Cc: Javier Carrasco <javier.carrasco.cruz@gmail.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3] cpupower: Make help command available for custom install dir
Date: Thu, 27 Jun 2024 11:33:03 -0600 [thread overview]
Message-ID: <c9df6637-6055-4668-b80b-a1a6e6be445e@linuxfoundation.org> (raw)
In-Reply-To: <20240627-fix-help-issue-v3-1-85318a3974e4@gmail.com>
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?
thanks,
-- Shuah
next prev parent reply other threads:[~2024-06-27 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 7:49 [PATCH v3] cpupower: Make help command available for custom install dir Roman Storozhenko
2024-06-27 17:33 ` Shuah Khan [this message]
2024-06-28 11:30 ` Roman Storozhenko
2024-06-28 19:45 ` Shuah Khan
2024-06-29 10:48 ` Roman Storozhenko
2024-07-01 19:40 ` Shuah Khan
2024-07-02 7:40 ` Roman Storozhenko
2024-07-02 18:52 ` Shuah Khan
2024-07-02 18:52 ` Roman Storozhenko
2024-07-02 18:57 ` Shuah Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c9df6637-6055-4668-b80b-a1a6e6be445e@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=romeusmeister@gmail.com \
--cc=shuah@kernel.org \
--cc=trenn@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox