We're still unable to reproduce this on a stock install of Raspberry Pi OS with rpi-connect running a single non-root user even with the Boot configuration in raspi-config set to "Console" (no autologin). We always see a systemd slice for the lingering user which allows rpi-connectd to run, e.g.
Can you please share any more information about your particular set up, especially regarding user accounts and systemd?
Are there any other applications running or certain bits of your configuration after imaging your storage that might affect this?
Code:
mudge@raspberrypizero:~ $ ps uxfUSER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMANDmudge 412 0.0 2.0 16436 9092 ? Ss 11:46 0:01 /lib/systemd/systemd --usermudge 413 0.0 0.8 35208 3932 ? S 11:46 0:00 \_ (sd-pam)mudge 432 5.3 3.8 543976 17072 ? Ssl 11:46 1:47 \_ /usr/bin/rpi-connectd -socket /run/user/1000/rpi-connect-wayvnc.sockmudge 1059 2.5 0.8 8428 3916 pts/0 Ss 12:19 0:00 | \_ /bin/bash -lmudge 1072 250 0.9 11704 4152 pts/0 R+ 12:20 0:00 | \_ ps uxfmudge 447 0.0 0.8 7348 3820 ? Ss 11:46 0:00 \_ /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-onlyAre there any other applications running or certain bits of your configuration after imaging your storage that might affect this?
Statistics: Posted by paulmu — Wed Nov 27, 2024 12:21 pm