Date: Thu, 14 Aug 2025 23:28:29 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: Sivasubramanian M <6.internet@gmail.com> Cc: freebsd-current@freebsd.org, fbsd@www.zefox.net Subject: Re: How to resume an interrupted frrleebsd-update install if indeed it is an interruption. Message-ID: <86ikipvbia.fsf@ltc.des.dev> In-Reply-To: <CAKsgsGzTxr0CJSwYWrW=v7thOQxDbV3fakzocB4ep_60_LDORA@mail.gmail.com> (Sivasubramanian M.'s message of "Fri, 15 Aug 2025 02:09:02 %2B0530") References: <CAKsgsGzTxr0CJSwYWrW=v7thOQxDbV3fakzocB4ep_60_LDORA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Sivasubramanian M <6.internet@gmail.com> writes: > Ran freebsd-update install. ( to 14.3 Release) Rebooted after kernel > update ( by the same command). While freebsd-update install was > running, checked du -sh in another terminal, mistyped the passwd and > then ^C and found on the first console " Installing updates .... doas > : in prompt_tty(): caught signal 2.1. Does this mean that ^C also > interrupted the update installation in progress in console 1? No. It's just a syslog message that was deemed important enough to be echoed to the console. I recommend a) always running freebsd-update inside screen or tmux, and b) never logging in on ttyv0, since that is where console messages go. > du -sh /var/db/freebsd-update remains unchangedcat 2.3 GB for over 45 > minutes. /var/db/freebsd-update is fully populated by the fetch or upgrade stage and will not grow (or shrink) noticeably while the install stage is running. And yes, we know freebsd-update is slow. There is a Rust implementation called freebsd-rustdate which is reputedly much faster, though I have never tried it myself. 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?86ikipvbia.fsf>