As you have spotted, the login program can be, and usually is, configured to time out if no input is received for a certain number of seconds. There are various motivations for this behaviour, ranging from wanting to keep unused dial-up lines clear to the world wanting you to clean your screen. There are, equally, reasons for not wanting it, as you have ...
Using BR2_ROOTFS_OVERLAY, make the guest /etc/inittab to contain:
instead of the default line of form:
console::respawn:/sbin/getty -L console 0 vt100
You can copy the default inittab from output/target/etc/inittab after the build.
I found this while studying the examples/inittab in Busybox 1_28_3 and found this, ...
If your system uses BusyBox init, and it doesn't have /etc/inittab, then it runs /etc/init.d/rcS at boot time. If this is a shell script, just add the environment definitions you want there. If this isn't a shell script, you can change your build to rename /etc/init.d/rcS.bin, and create a shell script /etc/init.d/rcS that ends with exec /etc/init.d/rcS.bin. ...
Apparently impossible without changing the source code.
Searching for login.defs or LOGIN_TIMEOUT yields indeed no relevant results and looking at loginutils/login.c it really seems like the value and the whole timer are hardcoded:
TIMEOUT = 60,
EMPTY_USERNAME_COUNT = 10,
/* Some users found 32 chars limit to be too low: */
I hope your backups are in good order.
In an initramfs recovery shell, you are already root, so you don't need sudo. The problem might be that the number of tools available within the initramfs is usually very restricted.
You might want to boot the system using an external boot media: a live USB/DVD/CD would probably work well, and would give you a nicer ...
If there a line in /etc/inittab like:
Then if you send SIGQUIT to init it will replace itself with /tmp/updater_stage2. To reload /etc/inittab after you have changed it send SIGHUP. You can replace /etc/inittab with a bind mount:
mount --bind /tmp/inittab /etc/inittab
kill -HUP 1
kill -QUIT 1
If there is no /etc/...
So it seems like busybox is getting signal for reboot but handling only after init scripts executed.
That is exactly how the init in BusyBox now works, yes. No, this is not configurable. You have to alter the program and re-build it.
Denys Vlasenko (2014-11-21). init: do not run shutdown/reexec actions from signal handler. BusyBox ...