Your message dated Sun, 7 Apr 2024 14:39:57 +0200
with message-id <[email protected]>
and subject line Re: Bug#565621: bash: ulimit -v documentation misleading
has caused the Debian Bug report #565621,
regarding bash: ulimit -v documentation misleading
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
565621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565621
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash
Version: 4.1-1
Severity: minor
In the Bash documentation on ulimit, it says this:
> ulimit [-HSTabcdefilmnpqrstuvx [limit]]
> Provides control over the resources available to the shell and
> to processes started by it, on systems that allow such control.
> ...
> -d The maximum size of a process's data segment
> ...
> -s The maximum stack size
> ...
> -v The maximum amount of virtual memory available to the
> shell
Now, the problem is that for the "-v" flag, it specifies that it affects
only the shell. This is made stronger by the contrast with the two
related flags, "-d" and "-s" which (according to the text on the top)
apply both to the shell and to processes started by the shell.
Now, in reality, the -v flag also affects processes started by the
shell, as you can see below:
$ echo $$
29307
$ ulimit -Sv 100000
$ ulimit -v
100000
$ bash
$ # We are now in a sub-shell, another process started by the first.
$ # Note the different PID number
$ echo $$
29335
$ # Now we check the ulimit of the sub-process
$ ulimit -v
100000
$ man bash
So, please delete the words " available to the shell" from the bash
manpage. They are incorrect.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-proposed-updates')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bash depends on:
ii base-files 5.0.0 Debian base system miscellaneous f
ii dash 0.5.5.1-3 POSIX-compliant shell
ii debianutils 3.2.2 Miscellaneous utilities specific t
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii libncurses5 5.7+20090803-2 shared libraries for terminal hand
Versions of packages bash recommends:
ii bash-completion 1:1.1-3 programmable completion for the ba
Versions of packages bash suggests:
pn bash-doc <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.0-6
On Sun, 17 Jan 2010 14:00:00 +0000 Greg Kochanski <[email protected]> wrote:
In the Bash documentation on ulimit, it says this:
> ulimit [-HSTabcdefilmnpqrstuvx [limit]]
> Provides control over the resources available to the shell and
> to processes started by it, on systems that allow such control.
> ...
> -d The maximum size of a process's data segment
> ...
> -s The maximum stack size
> ...
> -v The maximum amount of virtual memory available to the
> shell
Now, the problem is that for the "-v" flag, it specifies that it affects
only the shell. This is made stronger by the contrast with the two
related flags, "-d" and "-s" which (according to the text on the top)
apply both to the shell and to processes started by the shell.
Now, in reality, the -v flag also affects processes started by the
shell, as you can see below:
This has been improved in bash version 5.0-6 and later.
The manpage now states:
-v The maximum amount of virtual memory available to the shell
and, on some systems, to its children
Regards,
--
Gioele Barabucci
--- End Message ---
