Bug 609092 - zfcpdbf: Fix --dates option
zfcpdbf: Fix --dates option
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: s390utils (Show other bugs)
6.0
s390x Linux
low Severity medium
: rc
: ---
Assigned To: Dan Horák
Alex Sersen
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-29 08:09 EDT by Hendrik Brueckner
Modified: 2013-10-31 21:34 EDT (History)
6 users (show)

See Also:
Fixed In Version: s390utils-1.8.2-27.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-10 17:19:59 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
s390-tools-rhel6-zfcpdbf-dates.patch (909 bytes, patch)
2010-06-29 08:10 EDT, Hendrik Brueckner
no flags Details | Diff

  None (edit)
Description Hendrik Brueckner 2010-06-29 08:09:15 EDT
Description of problem:

Description: zfcpdbf: Fix --dates option
Symptom:     Running zfcpdbf with the option --dates returns "Unknown
             option: dates".
Problem:     The code expects --date, not the documented --dates option.
Solution:    Change zfcpdbf to expect --dates, as documented in the
             man page and in the usage information.
Comment 1 Hendrik Brueckner 2010-06-29 08:10:01 EDT
Created attachment 427659 [details]
s390-tools-rhel6-zfcpdbf-dates.patch
Comment 3 RHEL Product and Program Management 2010-06-29 08:23:15 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 8 releng-rhel@redhat.com 2010-11-10 17:19:59 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.