ping On Sat, 17 May 2025 11:13:36 +0900 Olaf Meeuwissen <[email protected]> wrote: > Dear Maintainer, > > After upgrading from 2.2.0-2 to 2.2.0-3, I noticed > > $ ps -HAf | grep [r]unsvdir > root 1738 1 0 10:24 ? 00:00:00 runsvdir -P > /etc/service log: run: 21: fuser: not found /etc/sv/getty-ttyS0/run: > 21: fuser: not found /etc/sv/getty-ttyS0/run: 21: fuser: not found > /etc/sv/getty-ttyS0/run: 21: fuser: not found > /etc/sv/getty-ttyS0/run: 21: fuser: not found > /etc/sv/getty-ttyS0/run: 21: fuser: not found > ./etc/sv/getty-ttyS0/run: 21: fuser: not found > /etc/sv/getty-ttyS0/run: 21: fuser: not found > /etc/sv/getty-ttyS0/run: 21: fuser: not found
Olaf, I'm still interested and available to understand and fix the issue that causes the restart loop of the getty service, but I need you to provide more info to understand what causes the problem > * do you have /dev/tty-S0 in you machine? > > * Also the run file does some greppin on /proc/cmdline to guess the > "right" serial console and that might be wrong as well: could you > print the value of $SGETTY variable in the runscript, just before > the exec line and see if that is something weird/wrong? > even better, if this comes (or is reproducible) from inside a container, you can provide me the commands to reproduce the issue myself. It's fine if it's a downstream that uses the debian package as is. Without further info I intend to close this bug on timeout in a couple of weeks or so. Best, Lorenzo
