On Thu, Aug 22, 2019 at 03:38:05PM +0200, Ulrich Windl wrote: > >>> systemd tag bot <donotreply-systemd-...@refi64.com> schrieb am 22.08.2019 > um > 13:56 in Nachricht <20190822115637.1.05c510c92b339...@refi64.com>: > > A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the > > tarball here: > > > > * On 64 bit systems, the "kernel.pid_max" sysctl is now bumped to > > 4194304 by default, i.e. the full 22bit range the kernel allows, > > up > > from the old 16bit range. This should improve security and > > robustness, as PID collisions are made less likely (though > > I doubt it's increasing robustness for any existing application as > pid_traditionally was 16 bit. I don't know if some applications try to > sprintf() a pid into a char[6], but if they do, it might cause an application > failure...
What kind of tradition would that be? Could you please point the specific standard and implentation? Everywhere I look pid_t is "signed integer type" which is implemented as 32 bits. -- Tomasz .. oo o. oo o. .o .o o. o. oo o. .. Torcz .. .o .o .o .o oo oo .o .. .. oo oo o.o.o. .o .. o. o. o. o. o. o. oo .. .. o. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
