DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4BL6PlfZ1816413 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 4BL6PlfZ1816413 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=pSG6DSZV X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 279D03858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1734762345; bh=ygWyEeSDozA5VwXoU9Fkm2EaSc5rMn9imlxeXp0y08g=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=pSG6DSZVOoAUpTLTtpa69iT+D+PupBlxfT6wmkQ/GBBJSJp6C+TT9hcWBhB7v7CEq syls6NU/TS+hjv2GPVkXSfagy0u0I68eKamnDoFZ2bzGr3EQitespPo7oTaVoCXJqt MJduwGjIrqiyKT7Vt+pl5TTWYFBf2F3SOIONmXpQ= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 273863858D3C ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 273863858D3C ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1734762276; cv=none; b=Sl7ViCyrNNjdwKYzh2MGUhUn35SiznDY91NENEtgUwP+3SRIv+ZrHobTiRwpReMXhXgTlzUiCScp7Je2BPGO/vskJb/uw/ldhtGyQiqEpLt7kfdj5FuwfWhHf1gKfK0acFidsuJ3e8Jz2e+asW/Fn9DzrTUiOvnk+aHza80QFHQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1734762276; c=relaxed/simple; bh=h8Q8qRh9Dc/yj9+0nk+0SbcAcSjvu7XIea1snmBvCkc=; h=Message-ID:Date:MIME-Version:Subject:To:From:DKIM-Signature; b=cOz1uWYpkrDG2DWr8BaWujYuaxs7x5a5YO2lhGw58we9rPwYS+lk2fAqhajbrtpFX7LNveeZ+dRYOm9wqhIEii2EKLpYw75usc28zclpNGA9aTRKFCC4CTfgcTfh9kac911m44r4STPBtt/WA2afrQpNuT7m9RPfpNQJWTy9YNs= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 273863858D3C Message-ID: Date: Fri, 20 Dec 2024 23:24:33 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: EPYC 144 core machine has issues with Cygwin PID wraparound Content-Language: en-CA To: cygwin AT cygwin DOT com References:

<6193fecd-9116-4182-82ff-a7bdcc5a6dbd AT SystematicSW DOT ab DOT ca> Organization: Systematic Software In-Reply-To: X-Rspamd-Server: rspamout06 X-Rspamd-Queue-Id: 1134980009 X-Stat-Signature: po9tjmps5oewbteirsxs5w93qz1pk9iw X-Session-Marker: 427269616E2E496E676C69734053797374656D6174696353572E61622E6361 X-Session-ID: U2FsdGVkX1/6+U4IT4SEgquHYqG206r1SWJarrnESgc= X-HE-Tag: 1734762240-711260 X-HE-Meta: U2FsdGVkX1/jr2YDwa7uOHgYUc87sFqeaxM6XcUM87lhIgD1RY+QU2IlqhW93beEb1kZie9tBJgMz4Wt9BC+cKsOQr2ari2nhRtgC7WhwYJYV9ULdpq+tSRuuC1IF1piVBYb0XIyu0/9XvVS9ki0bnlmetKYd5qjL8/VS4+wKx+42y2HYSEk3p1zLTlh3Kz4vXqqs9uxIbllXyMZoasvL+um1z+rLl/2aoxeW9VSe/TDC/NEDOYiuZq3jOA6hq7+hs2tA83tq0sbbr8J+zeXn+VGqo6DXauM+EHM/bTevYvSLsdlDrgbwiQ4R++hOlNOu60jY/hvNvgLUjVHVyBdOToSqeQPhkSEFMDF1sBSnd+G8lCtQ7DKr1bQtYy/jUqD3UqeHbhjLZjjjF/CVfugVQ== X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Brian Inglis via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Brian Inglis Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 4BL6PlfZ1816413 On 2024-12-20 04:58, Cedric Blancher via Cygwin wrote: > On Fri, 20 Dec 2024 at 01:31, Brian Inglis via Cygwin wrote: >> >> On 2024-12-19 16:42, Corinna Vinschen via Cygwin wrote: >>> On Dec 19 17:20, Cedric Blancher via Cygwin wrote: >>>> Good afternoon! >>>> >>>> We have a new AMD EPYC machine with 144 cores (upgraded from 8 core >>>> machine) running Windows 10 Enterprise, with a mixture of native Win32 >>>> apps+Cygwin. >>>> But the Cygwin apps cause trouble, as PID numbers get re-used too >>>> fast. We churn through ~~6912000 child processes EVERY HOUR, which now >>>> causes major problems with PID wraparounds in scripts and perl. >>>> >>>> 1. How can I increase the value at which pid-wraparound will happen? >>>> 2. How can I test for Cygwins max PID value? Cygwin does not have >>>> /proc/sys/kernel/pid_max >>> >>> We can't make the pid algorithm variable in terms of the max pid, so >>> I changed the maximum PID to the maximum pid on Linux, i.e., 4194304. >>> >>> Please check out the next test release cygwin 3.6.0-0.294.g363357c023ce. >> >> Run the attached to check your upgrade: >> >> $ gcc -o cyg_max_pid{,.c} && ./cyg_max_pid >> max pid 65536 > Can we please get an interface in /proc OR /bin/getconf to get/probe > the maximum pid value? Rename the program to sysctl and have it respond to arg kernel.pid_max with kernel.pid_max = 4194304? ;^> There appears to be no POSIX definition usable by getconf: why it is enabled by a CW_... value accessible via cygwin_internal(). Linux makes it available only under /proc/sys/kernel/pid_max tunables which Cygwin does not support as /proc/sys is for Windows objects. BSDs including MacOSX seem to hard code 99999 now (was 30000). Patches Gratefully Accepted! -- Take care. Thanks, Brian Inglis Calgary, Alberta, Canada La perfection est atteinte Perfection is achieved non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut -- Antoine de Saint-Exupéry -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple