https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271287
--- Comment #5 from Miroslav Lachman <000.f...@quip.cz> --- (In reply to John Baldwin from comment #4) Yes. Maybe use better wording in the panic message to tell the user "This file is broken now, you must fix it manually" too. 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 that cp failed. The biggest problem now is that etcupdate do not show any errors from the cp. 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. -- You are receiving this mail because: You are the assignee for the bug.
