0

When I tried to get the maximum socket buffer size (ulimit -b) on an Ubuntu Server 12.04.5 LTS, the ulimit tool throws this error message:

root@wsproducao:~# ulimit -b
-su: ulimit: -b: invalid option
ulimit: usage: ulimit [-SHacdefilmnpqrstuvx] [limit]

I've grabbed this option (-b) from man bash.

Why is there a difference between the options informed in ulimit's help command with those informed in man bash?

   ulimit [-HSTabcdefilmnpqrstuvx [limit]]
          Provides control over the resources available to the shell and to processes started by it, on systems that allow such control.  The -H and -S options specify that the
          hard  or  soft limit is set for the given resource.  A hard limit cannot be increased by a non-root user once it is set; a soft limit may be increased up to the value
          of the hard limit.  If neither -H nor -S is specified, both the soft and hard limits are set.  The value of limit can be a  number  in  the  unit  specified  for  the
          resource  or one of the special values hard, soft, or unlimited, which stand for the current hard limit, the current soft limit, and no limit, respectively.  If limit
          is omitted, the current value of the soft limit of the resource is printed, unless the -H option is given.  When more than one resource is specified, the  limit  name
          and unit are printed before the value.  Other options are interpreted as follows:
          -a     All current limits are reported
          -b     The maximum socket buffer size
          -c     The maximum size of core files created
          -d     The maximum size of a process's data segment
          -e     The maximum scheduling priority ("nice")
          -f     The maximum size of files written by the shell and its children
          -i     The maximum number of pending signals
          -l     The maximum size that may be locked into memory
          -m     The maximum resident set size (many systems do not honor this limit)
          -n     The maximum number of open file descriptors (most systems do not allow this value to be set)
          -p     The pipe size in 512-byte blocks (this may not be set)
          -q     The maximum number of bytes in POSIX message queues
          -r     The maximum real-time scheduling priority
          -s     The maximum stack size
          -t     The maximum amount of cpu time in seconds
          -u     The maximum number of processes available to a single user
          -v     The maximum amount of virtual memory available to the shell and, on some systems, to its children
          -x     The maximum number of file locks
          -T     The maximum number of threads
user3742266
  • 153
  • 1
  • 1
  • 6

2 Answers2

0

First thing I would think of is your man pages are hosed up...just a thought. I am on 14.04 and have and this has not changed for a long time Linux:

ulimit [-SHabcdefilmnpqrstuvxT]

doktoroblivion
  • 428
  • 3
  • 14
0

From help ulimit:

[...] Not all options are available on all platforms. [...]

There is not RLIMIT_SBSIZE on linux, therefore the -b option to ulimit is not implemented there, only on platforms that support it (like bsd).

Unfortunately the error message here is a bit cryptic, it would be better if it was "-b not supported on this platform" or something similar.

The man page in this case list all possible options, the usage hint only seems to display the available options.

mata
  • 67,110
  • 10
  • 163
  • 162