Date: Tue, 14 Oct 2025 02:48:07 +0200
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Olivier Certner <olce@freebsd.org>, fs@freebsd.org, current@freebsd.org
Subject: Re: openat("./...", O_CREAT) fails even though the directory exists
Message-ID: <86zf9u5mwo.fsf@ltc.des.dev>
In-Reply-To: <CAJ-Vmo=x7w-Us8fwG6O6k5qJ_QV0bCJgxF4mAMFFQd2Y4c7yeQ@mail.gmail.com> (Adrian Chadd's message of "Mon, 13 Oct 2025 11:06:02 -0700")
References: <aOy5LUUu5DCwY_XZ@amaryllis.le-fay.org> <2507674.THHZn3L5Ee@ravel> <aOzF-JAOyg-T-Ule@amaryllis.le-fay.org> <6142242.Zv9zXsTiuT@ravel> <aOzTBEsi_KKFDiwa@amaryllis.le-fay.org> <CAJ-Vmo=x7w-Us8fwG6O6k5qJ_QV0bCJgxF4mAMFFQd2Y4c7yeQ@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Adrian Chadd <adrian@freebsd.org> writes: > I'm curious - why are we NOT restarting services after an upgraded package? We've never done so in the past, neither for base nor for ports (or packages), except that we started restarting sshd in freebsd-update(8) a few years ago because sshd will stop accepting new connections if the on-disk binary gets desynchronized from the running daemon, so you can easily lock yourself out of a system by running freebsd-update remotely, cf. <https://bugs.freebsd.org/263489>. DES -- Dag-Erling Smørgrav - des@FreeBSD.orghome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86zf9u5mwo.fsf>