Date: Wed, 08 Feb 2023 07:43:02 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyMjQ5NzVdIHNodXRkb3duKDgpIG5lZWRzIHRvIHdhaXQg?= =?UTF-8?B?bG9uZ2VyIGZvciBzd2Fwb2ZmIHRvIGF2b2lkIGEg4oCcQ2Fubm90IGFsbG9j?= =?UTF-8?B?YXRlIG1lbW9yeeKAnSBlcnJvcg==?= Message-ID: <bug-224975-227-jadbzmtM3e@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224975-227@https.bugs.freebsd.org/bugzilla/> References: <bug-224975-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224975 Volodymyr Kostyrko <arcade@b1t.name> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arcade@b1t.name --- Comment #4 from Volodymyr Kostyrko <arcade@b1t.name> --- Well, some device might be not local, and that means stopping some daemons = will make us lose those devices and part of active memory. Imagine you are runni= ng a diskless host that has swap somewhere on rSCSI or gated. Next there's a phase when kernel stops all disk activity, meaning that noth= ing can be extracted from swap at this time. Therefore all remaining activities will only be successful if you don't hit an evicted page. Well, this is qui= te unlikely, but in case you have a notebook or running on UPS you definitely don't want extra possibility for system to crash, wait for timeout, write c= ore, reset, reboot, and be ready to poweroff again. Always better be safe then sorry. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224975-227-jadbzmtM3e>