Using net_fs_list="" and rc_tty_number=4 in rc.conf instead of default left me with a system which boots properly but after a few minutes logged in (in console) logs out all regular users (after killing all their running processes) and looses hold of many daemons and mounts apart from a still writable / (not rootfs) With rc.conf reverted to default this ceased to happen. Reproducible: Always Steps to Reproduce: 1. Update to >=baselayout-2.0 2. Set net_fs_list="" and rc_tty_number=4 in /etc/rc.conf 3. Reboot Actual Results: As a user: Applications quit (dmesg reports "<application> used maximum stack depth") Seconds later: Logout occurs Upon login: Mounts apart from / are gone Nothing out of the ordinary in dmesg, apart from significant messages of used stack depth (see attached).
Created attachment 250625 [details] dmesg
(In reply to comment #0) > Using net_fs_list="" and rc_tty_number=4 in rc.conf instead of default left me > with a system which boots properly but after a few minutes logged in (in > console) logs out all regular users (after killing all their > running processes) > and looses hold of many daemons and mounts apart from a still writable / (not > rootfs) > With rc.conf reverted to default this ceased to happen. There are actually 3 possible combinations of settings that could be causing this: 1) net_fs_list="" and rc_tty_number unchanged from default 2) rc_tty_number=4 and net_fs_list unchanged from default 3) net_fs_list="" and rc_tty_number=4 These settings are not related to each other, so I suspect that only one of them might be causing the issue. Can you please test the settings I have listed and re-open this bug and report back which one causes the issue?
