Sujet : Re: pid ranges (Was: (bash) How (really!) does the "current job" get determined?)
De : janis_papanagnou+ng (at) *nospam* hotmail.com (Janis Papanagnou)
Groupes : comp.unix.shellDate : 07. Oct 2024, 03:58:56
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vdviph$1io9a$1@dont-email.me>
References : 1 2 3 4 5
User-Agent : Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
On 05.10.2024 19:13, Kenny McCormack wrote:
In article <slrnvg2nc2.2dut.naddy@lorvorc.mips.inka.de>,
Christian Weisgerber <naddy@mips.inka.de> wrote:
...
time frame. Nowadays, we have 22 bit pids, so it is even less likely (*).
>
"We" do? Offhand, I don't know the size of pid_t, much less how
much of its numerical range is actually used.
On Linux, check out: /proc/sys/kernel/pid_max
As I read the various posts on the subject, 15 bit is still the limit on 32
bit systems, 22 bit on 64 bit systems. But, of course, YMMV.
Hmm.. - my [a bit rusty] 64 bit Linux displays 32768 (15 bit).
(Not that I had anytime needed more than a fraction of these;
currently "only" about 2%.)
Janis
[...]