From nobody Wed Jun 24 16:09:39 2026 X-Original-To: freebsd-pkgbase@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4gln2H39hYz6jQT5 for ; Wed, 24 Jun 2026 16:09:43 +0000 (UTC) (envelope-from the.lists@mgm51.com) Received: from oneyou.mgm51.net (oneyou.mgm51.net [174.136.99.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (secp384r1) client-digest SHA384) (Client CN "oneyou.mgm51.net", Issuer "Mike's Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4gln2G53ZJz3Gnq for ; Wed, 24 Jun 2026 16:09:42 +0000 (UTC) (envelope-from the.lists@mgm51.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=mgm51.com header.s=mgm51.com-10 header.b=d6FyCtUa; dmarc=pass (policy=reject) header.from=mgm51.com; spf=pass (mx1.freebsd.org: domain of the.lists@mgm51.com designates 174.136.99.202 as permitted sender) smtp.mailfrom=the.lists@mgm51.com Received: from sentry.mgm51.net (sentry.mgm51.net [IPv6:2001:558:6017:e3:1130:5cc5:3dee:2458]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "sentry.mgm51.net", Issuer "Mike's Certificate Authority" (verified OK)) by oneyou.mgm51.net (Postfix) with ESMTPS id 4gln2D3R4rzHh0G for ; Wed, 24 Jun 2026 12:09:40 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mgm51.com; s=mgm51.com-10; t=1782317380; bh=h2p65h0fHNFuEfigFeVIl9bFOpd+9Jr13/yAKCBi7aQ=; h=Date:Subject:From; b=d6FyCtUa1yVIdEv2tCvt5KtvQyDG3pj2FVpGY6ToiPwh4xncZvg4CBc766H83e9fK VY3iEU1EZ+NqkHxdFr3oVReGKjtGxQZepiJ0yBvdk6BM15IyaTh5LPxnKwN0/jBY/S GOvnUtwywo7+e0om9c1JRK7DbDm1J3fTHCobBa0t3aBMZoGk8oF1xy9daYP6vQAkyG VxVLmYBbMiiOE5b28DBo+CfeHb5ApIxyB/OZH5DDNlv4lWjVIo6aSb1o+fZ746r/4p lEr78FtCLFNtaruYoULx+avccisU/COgwYQzjLBx/cJdnhWxbSJwTx9Z+tLrBwQUd2 OvJm0dblcSBIg== Received: from [10.11.2.100] (bigbloat.24cl.home [10.11.2.100]) by sentry.mgm51.net (Postfix) with ESMTP id 4gln2C3KV3zRcq3 for ; Wed, 24 Jun 2026 12:09:39 -0400 (EDT) Message-ID: Date: Wed, 24 Jun 2026 12:09:39 -0400 List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Moving to pkg-based in 15.1 ... To: freebsd-pkgbase@FreeBSD.org References: <86a4sot2l4.fsf@ltc.des.dev> <27027cff-3c3b-41c6-a45f-f5e76e673011@mgm51.com> <865x39r5aj.fsf@ltc.des.dev> Content-Language: en-US From: Mike In-Reply-To: <865x39r5aj.fsf@ltc.des.dev> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-6.70 / 15.00]; DWL_DNSWL_MED(-2.00)[mgm51.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[mgm51.com,reject]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_DKIM_ALLOW(-0.20)[mgm51.com:s=mgm51.com-10]; R_SPF_ALLOW(-0.20)[+ip4:174.136.99.202]; RCVD_IN_DNSWL_MED(-0.20)[174.136.99.202:from]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:25795, ipnet:174.136.96.0/20, country:US]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-pkgbase@FreeBSD.org]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-pkgbase@freebsd.org]; DKIM_TRACE(0.00)[mgm51.com:+] X-Spamd-Bar: ------ X-Rspamd-Queue-Id: 4gln2G53ZJz3Gnq On 6/23/2026 5:10 AM, Dag-Erling Smørgrav wrote: > Mike writes: >> Agreed. I have always restarted all daemons after an update, and did >> a reboot when I saw some things updated that I knew needed an reboot >> (e.g., kernel update). > > Here's a trick... > > You can use procstat -v to dump the memory map of any process, which > will show you which binary and libraries it has loaded: > > $ procstat -v $$ > PID START END PRT RES PRES REF SHD FLAG TP PATH > 91099 0x29bee374e000 0x29bee3759000 r-- 8 38 33 11 CN--- vn /bin/sh > 91099 0x29bee3759000 0x29bee3777000 r-x 30 38 33 11 CN--- vn /bin/sh > 91099 0x29bee3777000 0x29bee3778000 r-- 1 0 1 0 CN--- vn /bin/sh > [...] > 91099 0x29c706072000 0x29c7060f7000 r-- 78 332 662 274 CN--- vn /lib/libc.so.7 > 91099 0x29c7060f7000 0x29c706242000 r-x 240 332 662 274 CN--- vn /lib/libc.so.7 > 91099 0x29c706242000 0x29c70624c000 r-- 10 0 1 0 CN--- vn /lib/libc.so.7 > 91099 0x29c70624c000 0x29c706253000 rw- 7 0 1 0 CN--- vn /lib/libc.so.7 > [...] > 91099 0x49b7fa342000 0x49b7fa348000 r-- 6 29 525 137 CN--- vn /libexec/ld-elf.so.1 > 91099 0x49b7fa348000 0x49b7fa35f000 r-x 23 29 525 137 CN--- vn /libexec/ld-elf.so.1 > 91099 0x49b7fa35f000 0x49b7fa360000 r-- 1 0 1 0 CN--- vn /libexec/ld-elf.so.1 > > If any of these are replaced or deleted after the process starts, the > connection between vnode and path is lost and procstat no longer > displays the path: > > $ cp /bin/sh . > $ ./sh > $ procstat -v $$ | head -4 > PID START END PRT RES PRES REF SHD FLAG TP PATH > 91107 0x1e80b9a00000 0x1e80b9a0b000 r-- 11 41 3 1 CN--- vn /home/des/sh > 91107 0x1e80b9a0b000 0x1e80b9a29000 r-x 30 41 3 1 CN--- vn /home/des/sh > 91107 0x1e80b9a29000 0x1e80b9a2a000 r-- 1 0 1 0 CN--- vn /home/des/sh > $ rm -f ./sh > $ procstat -v $$ | head -4 > PID START END PRT RES PRES REF SHD FLAG TP PATH > 91107 0x1e80b9a00000 0x1e80b9a0b000 r-- 11 41 3 1 CN--- vn > 91107 0x1e80b9a0b000 0x1e80b9a29000 r-x 30 41 3 1 CN--- vn > 91107 0x1e80b9a29000 0x1e80b9a2a000 r-- 1 0 1 0 CN--- vn > > So you can use something like this to list all processes which have an > executable mapping where the original path is gone: > > # ps $(procstat -va | awk '$4 == "r-x" && $NF == "vn" { print $1 }') > > This will give you a better idea of what actually needs restarting than > just guessing. > > DES That looks interesting. I'll check it out. For many years I have been using service -R to restart the daemons, and that has worked for me. Thanks again.