Bug 1108340

Description of problem:

The shell allows you to get access to more results from a search, by entering m.

However the straight CLI does not, you get 50 and it dumps out.

If I'm doing proactive queries on subject I want to get the full set so I automate scripts to proactively check for new kcs/issues to review.  With having a limit return I can't do that.

This is command problem with cli tools that interface with backends.

e.g.
There appears to be a limitation on results returned with the ipa cli can this be modified
https://access.redhat.com/site/solutions/261023

In the example above there's db/slapd limit and a client cli limit and a timelimit.  

This ensures that from cli you can get a many results as possible up to the limit of Strata max.

Then it can be on the user to see if they are hitting that max to determine whether fine tuning their query is required.

[dsulliva@localhost ~]$ redhat-support-tool search "kdump" | grep Title | wc -l
50

[dsulliva@localhost ~]$ redhat-support-tool search "kdump"
Title:   Kdump cannot start when booting the system which error is kdump: mkdumprd: failed to make kdump initrd
ID:      180113                                                      
State:   Unverified: This solution has not yet been verified to work by Red Hat customers.
URL:     https://access.redhat.com/site/solutions/180113             

...

 50 [ 392443:VER] Kdump wrongfully states that the crashkernel parameter is not specified - RHEL 5
 51 [  47111:UNV] kdump kernel hangs during bringing up bnx2x interface
 52 [  62354:VER] kdump warning to increase reserved memory
 53 [ 198343:VER] I blacklisted a module in /etc/kdump.conf, why is it still loaded in the kdump environment?
 54 [ 267023:VER] Start of kdump Fails with " Could not find a free area of memory of 5f3001 bytes... ELF exec load failed"
 55 [  56051:VER] What is the use of "default" parameter in kdump.conf file ?
 56 [  47470:VER] How am I aware vmcore is created by kdump.
 57 [  47346:UNV] kdump rebooted or dropped into shell before saving vmcore
 58 [  43316:VER] Enabling kdump on RHEL 6 gives the error : "Memory for crashkernel is not reserved"
 59 [ 237303:VER] [RHEL5] Kdump Hangs on CCISS Module.
59 of 100 solutions displayed. Type 'm' to see more, 'r' to start from the beginning again, or '?' for help with the codes displayed in the above output.
Select a Solution:



Version-Release number of selected component (if applicable):

latest version


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

It would be nice to document the Strata max result return as well