Re: install/59573: 11.0_BETA install leaves behind /etc/rc.conf.bak.* files

["Steve Rikli via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR install/59573; it has been noted by GNATS.

From: Steve Rikli <sr%genyosha.net@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: install/59573: 11.0_BETA install leaves behind
 /etc/rc.conf.bak.* files
Date: Mon, 4 Aug 2025 17:51:23 -0700

 Turns out this issue it not specific to 11.0_BETA; I freshly-installed
 another VM with 10.1 and also saw an /etc/rc.conf.bak.* file.
 
 I suspect it's related to steps from "Configure additional items" menu,
 likely an intermittent failure during "configure the network", like a
 temporary inability to get the client hostname from the local DHCP
 server, if I select the option to autoconfigure network.
 
 I noticed for that sysinst menu, if the hostname is pre-filled-in
 (because it was supplied by DHCP server during autoconfigure), I don't
 end up with an rc.conf.bak.* file.
 
 But if I need to manually enter hostname after autoconfigure, presumably
 because the installation client didn't get its hostname from DHCP server
 for some reason, then the empty rc.conf.bak.* file is left behind.
 
 If this sounds plausible I can try to replicate, e.g. by explicitly not
 sending "option host-name" or similar to the DHCP client from the
 server.
 
 Whatever the ultimate cause, it seems like sysinst should try to clean
 up after itself and remove these temp files at some point before exit.