Re: [systemd-devel] Is it a bug of manager->n_on_console?

2017-12-26 Thread piliu
When trying to interact with a emergency shell, this bug brights trouble by dumping endless status message to console On 12/25/2017 01:31 PM, piliu wrote: > Hi, > > When debugging with a shell, manager_status_printf() always prints "A > start job...". After tracing the systemd's code, I found in

Re: [systemd-devel] Using sysusers to setup a new system

2017-12-26 Thread Lennart Poettering
On Sa, 23.12.17 00:33, Sébastien Luttringer (se...@seblu.net) wrote: > The first issue[1] is to be able to define the root user shell. > Currently, sysusers.d/basic.conf provides a nologin shell, which prevent root > to login and execute commands (even via sudo). We cannot override the >

Re: [systemd-devel] Using sysusers to setup a new system

2017-12-26 Thread Lennart Poettering
On Di, 26.12.17 11:45, Jérémy Rosen (jeremy.ro...@smile.fr) wrote: > > The second issue[2] is about the lp group defined in > > /sysusers.d///basic.conf/. Because the /cups/ Arch package set rights on > > files based on the lp group it needs a static gid (pacman requirement). > > lp defined in

Re: [systemd-devel] Using sysusers to setup a new system

2017-12-26 Thread Jérémy Rosen
Hello Sébastian On 23/12/2017 00:33, Sébastien Luttringer wrote: Hello, On the way to rely on /systemd-sysusers/ to create *all* users in a fresh Arch Linux installation, I'm stuck with two issues[1][2]. The key idea was to rely on /systemd-users/ to create them all and start with empty