From: Dilger, Andreas <andreas.dilger@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Lustre and libreadline
Date: Thu, 4 Jun 2015 11:21:09 +0000 [thread overview]
Message-ID: <D1959036.F52DC%andreas.dilger@intel.com> (raw)
In-Reply-To: <20150603224901.GB10033@llnl.gov>
On 2015/06/03, 4:49 PM, "Ned Bass" <bass6@llnl.gov> wrote:
>On Wed, Jun 03, 2015 at 09:07:11PM +0000, Simmons, James A. wrote:
>> >You say you just install the library and not the utils, but do you
>> >specifically build without the utils? Is there some existing config
>> >option for that? (Hoping to save myself some grepping...) Otherwise,
>> >I'll have to add in that option.
>> >
>> >It also seems that readline-devel isn't available for the Intel Xeon
>>Phi
>> >chips (or at least Cray doesn't have it in our build setup).
>>
>> This is just papering over the real problem. The utilites should be
>>using
>> getopt() instead. The only thing Parse does that is non standard is
>> an interactive command line. The only place I have ever used that is
>> for lnet selftest. Does lfs really need an interactive command line?
>> I think not.
>
>I concur. There a few lctl commands that can only be run today in the
>interactive mode because they rely on earlier commands. For example,
>"conn_list" requires that you first run "network". Such commands should
>be updated to use sub-arguments rather than relying on previous
>commands.
This is handled by having a "command" named "--net" that runs the next
command (e.g. "conn_list") so that it can be run from the command-line.
That can definitely be replaced by getopt. I don't think interactive mode
is used very much anymore, so would probably be ok to remove from lctl.
Cheers, Andreas
--
Andreas Dilger
Lustre Software Architect
Intel High Performance Data Division
next prev parent reply other threads:[~2015-06-04 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 18:32 [lustre-devel] Lustre and libreadline Patrick Farrell
2015-06-03 18:57 ` Ned Bass
2015-06-03 20:27 ` Patrick Farrell
2015-06-03 20:57 ` Ned Bass
2015-06-03 21:07 ` Simmons, James A.
2015-06-03 22:49 ` Ned Bass
2015-06-04 11:21 ` Dilger, Andreas [this message]
2015-06-04 17:37 ` Ned Bass
2015-06-04 17:47 ` Ned Bass
2015-06-05 17:15 ` Dilger, Andreas
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=D1959036.F52DC%andreas.dilger@intel.com \
--to=andreas.dilger@intel.com \
--cc=lustre-devel@lists.lustre.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.