Bug 1163398
Summary: | [RFE] Include default check-period value in rhsm-icon --help | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Rehana <redakkan> |
Component: | subscription-manager | Assignee: | William Poteat <wpoteat> |
Status: | CLOSED ERRATA | QA Contact: | John Sefler <jsefler> |
Severity: | unspecified | Docs Contact: | |
Priority: | low | ||
Version: | 6.6 | CC: | bkearney, csnyder, dgoodwin, mstead, salmy, wpoteat |
Target Milestone: | pre-dev-freeze | Keywords: | FutureFeature |
Target Release: | 6.8 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-10 20:35:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1209535 |
Description
Rehana
2014-11-12 15:52:35 UTC
I just want to clarify that there is actually a hard coded 4 minute delay for the initial check when rhsm-icon is started. If check immeidately is false, then a 4 minute delay is used before the initial check, thereafter the --check-period is used. The default is equivalent to one day. [root@jsefler-os7 ~]# rhsm-icon --help Usage: rhsm-icon [OPTION...] Help Options: -h, --help Show help options --help-all Show all help options --help-gtk Show GTK+ Options Application Options: -c, --check-period how often to check for validity (in seconds) -d, --debug show debug messages -f, --force-icon=TYPE force display of the icon (expired, partial or warning) -i, --check-immediately run the first status check right away --display=DISPLAY X display to use TODO... Please change the --check-period description to: how often to check for validity (in seconds) (defaults to one day) Please change the --check-immediately description to: run the first status check right away, otherwise a 4 minute delay is used before the start of the initial check period Please update the man page to include these defaults. The 4 minute delay is already presented in the man page. Current help output: rhsm-icon --help Usage: rhsm-icon [OPTION...] Help Options: -h, --help Show help options --help-all Show all help options --help-gtk Show GTK+ Options Application Options: -c, --check-period how often to check for validity (in seconds; default is one day) -d, --debug show debug messages -f, --force-icon=TYPE force display of the icon (expired, partial or warning) -i, --check-immediately run the first status check without delay (otherwise wait 4 minutes) --display=DISPLAY X display to use master commit 47b84fe71cc28a71d278559d15d2e54b9452d7ac retested on , subscription management server: 0.9.51.11-1 subscription management rules: 5.15 subscription-manager: 1.16.7-1.el6 python-rhsm: 1.16.5-1.el6 Observed that now the default check period is mentioned for the options --check-period and --check-immediately 1) on the help # rhsm-icon --help Usage: rhsm-icon [OPTION...] Help Options: -h, --help Show help options --help-all Show all help options --help-gtk Show GTK+ Options Application Options: -c, --check-period how often to check for validity (in seconds; default is one day) -d, --debug show debug messages -f, --force-icon=TYPE force display of the icon (expired, partial or warning) -i, --check-immediately run the first status check without delay (otherwise wait 4 minutes) --display=DISPLAY X display to use 2) on the man page <snip> -c, --check-period Sets the interval to use between checks for the product subscription status. The value is in seconds and the default is one day. --i, --check-immediately Runs the status check process immediately when the command is invoked. Otherwise, there is a four (4) minute delay before running the initial check. Marking Verified!!! Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0797.html |