Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1882695

Summary: Manpage of find is incomplete regarding printf options
Product: Red Hat Enterprise Linux 8 Reporter: Steffen Froemer <sfroemer>
Component: findutilsAssignee: Lukáš Zaoral <lzaoral>
Status: CLOSED MIGRATED QA Contact: Radka Brychtova <rskvaril>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.2CC: kdudka, rskvaril
Target Milestone: rcKeywords: ManPageChange, MigratedToJIRA, Patch, Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: findutils-4.6.0-22.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-29 12:39:18 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:

Description Steffen Froemer 2020-09-25 11:01:04 UTC
Description of problem:
The list of possible option for printf format of File access time isn't complete regarding strftime options.

Version-Release number of selected component (if applicable):
findutils-4.6.0-20.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. `man find`
2. search for %AF in printf section
3.

Actual results:
The option is not listed

   737         -printf format
…
  776                %Ak    File's last access time in the  format  specified  by  k,  which  is
   777                       either `@' or a directive for the C `strftime' function.  The possi‐
   778                       ble values for k are listed below; some of them might not be  avail‐
   779                       able  on  all systems, due to differences in `strftime' between sys‐
   780                       tems.
...
815                       Date fields:
   816
   817                       a      locale's abbreviated weekday name (Sun..Sat)
   818
   819                       A      locale's  full  weekday name, variable length (Sunday..Satur‐
   820                              day)
   821
   822                       b      locale's abbreviated month name (Jan..Dec)
   823
   824                       B      locale's full month name, variable length (January..December)
   825
   826                       c      locale's date and time (Sat Nov 04 12:02:33 EST  1989).   The
   827                              format is the same as for ctime(3) and so to preserve compat‐
   828                              ibility with that format, there is no fractional part in  the
   829                              seconds field.
   830
   831                       d      day of month (01..31)
   832
   833                       D      date (mm/dd/yy)
   834
====>  HERE "F" is missing
   835                       h      same as b
   836

Expected results:
Either the complete list of strftime options or limited list with redirect to strftime.

Additional info:
https://man7.org/linux/man-pages/man3/strftime.3.html

Comment 2 Kamil Dudka 2020-10-02 08:39:36 UTC
(In reply to Steffen Froemer from comment #0)
>    737         -printf format
> …
>   776                %Ak    File's last access time in the  format specified  by  k,  which  is
>    777                       either `@' or a directive for the C `strftime' function.  The possi‐
>    778                       ble values for k are listed below; some of them might not be  avail‐
>    779                       able  on  all systems, due to differences in `strftime' between sys‐
>    780                       tems.

The above text already refers to the `strftime` function.

Are you proposing to change wording of the text somehow?

Comment 3 Steffen Froemer 2020-10-06 11:27:43 UTC
(In reply to Kamil Dudka from comment #2)

> Are you proposing to change wording of the text somehow?

Yes, I would change the wording. The text says:
 
 > The possible values for k are listed below; some of them might not be  available  on  all systems, due to differences in `strftime' between systems.

This means, the parameters listed in the manpage of `find` are the only ones which are supported out of the whole list of available parameters in strftime. This is wrong.
Better to say, "Below is an excerpt of possible values for k. For full list please refer to documentation of `strftime`*

*typically I guess the manpage of strftime on different systems does only consist the list of supported values, so an exception of unsupported values can be left out.

Does this make sense?

Comment 4 Kamil Dudka 2020-10-06 15:17:10 UTC
Thanks!  I have proposed a patch upstream:

https://lists.gnu.org/archive/html/bug-findutils/2020-10/msg00000.html

Comment 5 Kamil Dudka 2020-10-07 11:09:41 UTC
upstream commit: https://git.savannah.gnu.org/cgit/findutils.git/commit/?id=efa4554930

Comment 14 RHEL Program Management 2023-11-29 12:36:31 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 15 RHEL Program Management 2023-11-29 12:39:18 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.