Hi, Sent it too early.
On Wed, 2023-11-08 at 15:22 +0900, Osamu Aoki wrote: Hi, This is a good point to rethink description. > On Sat, 2023-09-23 at 15:31 -0400, Jonathan Kamens wrote: > > > > > Package: debmake-doc > > > > > Version: 1.17-7 > > > > > Severity: minor > > > > > > > > > > 1) Section 3.6 of the debmake doc says to run `adduser > > > > > <your_user_name> > > > > > sbuild` but there should be `sudo` at the beginning of that command. Yes. > But a new question is should I use `adduser`? It is not essential. Maybe it's > time to start using distribution non-dependent `usermod` here. > > > > > > 2) It also says "Logout and login to check you are a member of sbuild > > > > > group using id command." I don't know how universal this is, but if a > > > > > user has done `loginctl enable-linger` or has a user-level systemd > > > > > daemon configured, logging out logging back in won't work; they still > > > > > won't be in the group. They would need to either reboot or run `kill > > > > > -TERM -1` (NOT as root) to make all of their processes die and thereby > > > > > get the user-level systemd to restart. I know you're trying to keep > > > > > the guide simple so you you may not want to get into the nitty-gritty > > > > > details, but perhaps it is worth mentioning that if logging out and > > > > > logging back in doesn't work the user should try restarting their > > > > > computer. > What I knew were $ sudo usermod -aG sbuild USER $ sudo shutdown -r now -> This hard reboot from UEFI or $ sudo usermod -aG sbuild USER $ killall systemd -> This is soft reboot only systemd I don't know the latter has any bad side effects. Otherwise this is quicker. Your trick seem to be cleaner $ sudo usermod -aG sbuild USER $ kill TERM -TERM -1 Considering -TERM is -15, this may be redundant. Do you need this? Kill manpage has kill -9 -1 Kill all processes you can kill. -9 is SIGKILL. All these kill commands seem to work without going into hard reboot. Osamu
