Date: Mon, 08 May 2023 17:56:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 271287] etcupdate silently installs empty files / unhandled error in install_new() Message-ID: <bug-271287-227-CnCEQPrEGO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271287-227@https.bugs.freebsd.org/bugzilla/> References: <bug-271287-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=3D271287 --- Comment #5 from Miroslav Lachman <000.fbsd@quip.cz> --- (In reply to John Baldwin from comment #4) Yes. Maybe use better wording in the panic message to tell the user "This f= ile is broken now, you must fix it manually" too.=20 Thinking about it again, this kind of error message fits this specific case only but the cp can fail for many other reasons - /etc/ can be read only - = and in this case the target file will be intact but user still need to know tha= t cp failed. The biggest problem now is that etcupdate do not show any errors from the c= p. I was not noticed about anything and ended up with more than 80 files broken. If etcupdate stop on the first copy error, tell the user "Houston, we have a problem", then user can take some actions to fix it before reboot. --=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-271287-227-CnCEQPrEGO>