Date: Mon, 4 May 2026 13:21:51 -0700 From: Doug Hardie <bc979@lafn.org> To: Frank Leonhardt <freebsd-doc@fjl.co.uk> Cc: questions@freebsd.org Subject: Re: Console output during boot Message-ID: <D09394FD-5F3A-4162-9569-4A8212F064F8@sermon-archive.info> In-Reply-To: <880e3e21-061f-4d2b-a514-13c6905bcd05@fjl.co.uk> References: <7136899E-4CC4-414D-A4CC-CD2C11C51132@sermon-archive.info> <880e3e21-061f-4d2b-a514-13c6905bcd05@fjl.co.uk>
index | next in thread | previous in thread | raw e-mail
> On May 2, 2026, at 08:52, Frank Leonhardt <freebsd-doc@fjl.co.uk> wrote: > > On 30/04/2026 01:30, Doug Hardie wrote: >> I have one server (Raspberry Pi 4) which during boot shows all the hardware configuration, but then stops until the Login prompt appears. The other servers show the startup of each service and various other outputs. There is a 10 minute gap on the one server and I would like to see where it is during that process for that time. I have tried to find differences between the server configurations and haven't found the one that controls the startup output. What controls that? Thanks, >> >> > As no one else has said anything, all I can think of is the rc_startmsgs variable in rc.conf. This defaults to "yes", meaning display messages like Starting cron, Starting sshd and so on. Are these what you're missing? No. rc_startmsgs is set and rc_quiet is not set. > You say the config is the same, and therefore rc.conf is the same, but this is an override for /etc/defaults/rc.conf. > Have a good recursive grep around for anything that mentions rc_startmsgs (easy when you have the name!) > There's a boot_mute setting in loader.conf but I think that suppresses hardware probe stuff only. loader.conf man page says the console "nullconsole" command only affects the loader output. I am seeing all the loader output. > You can also turn up the verbosity by setting rc_debug and rc_info to "yes". Added both of them and there was no change. > But if it's the Starting.... messages you're not seeing then rc_stargmsgs is what suppresses them. My guess, FWIW, is you've got a DNS resolver issue - but I don't use a Raspberry Pi. > Regards, Frank. ntpd doesn't seem to have an issue with DNS. The DNS server is on the LAN. -- Doughome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D09394FD-5F3A-4162-9569-4A8212F064F8>