+++ This bug was initially created as a clone of Bug #1112709 +++

+++ This bug was initially created as a clone of Bug #1112708 +++

Description of problem:

The fact, that since bash-4.0

j.  The block multiplier for the ulimit -c and -f options is now 512 when in
    Posix mode, as Posix specifies.

is not reflected in man page.

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

bash-4.1.2-14.el6.x86_64  (and higher, including upstream bash-4.3)

How reproducible:

Always

Steps to Reproduce:
1. man bash
2.
3.

Actual results:

              If limit is given, it is the new value  of  the  specified
              resource (the -a option is display only).  If no option is
              given, then -f is assumed.  Values are in 1024-byte incre-
              ments, except for -t, which is in seconds, -p, which is in
              units of 512-byte blocks, and -T, -b, -n,  and  -u,  which
              are  unscaled  values.   The  return status is 0 unless an
              invalid option or argument is supplied, or an error occurs
              while setting a new limit.


Expected results:

Something like:

              If limit is given, it is the new value  of  the  specified
              resource (the -a option is display only).  If no option is
              given, then -f is assumed.  Values are in 1024-byte incre-
              ments, except for -t, which is in seconds, -p, which is in
              units of 512-byte blocks, and -T, -b, -n,  and  -u,  which
              are  unscaled  values.   The  return status is 0 unless an
              invalid option or argument is supplied, or an error occurs
              while setting a new limit. In POSIX Mode  512-byte  blocks
              are used for the `-c' and `-f' options.


Additional info:

The difference for POSIX mode is covered by bash.info in

6.11 Bash POSIX Mode

...

 42. The `ulimit' builtin uses a block size of 512 bytes for the `-c'
     and `-f' options.

...


I guess there will be more differences (but not huge difference in size in bash case) between man and info pages that may cause user confusion. Is there any reason, why those are not in sync? Would it be feasible to suggest upstream both man and info being generated from one source?