On Mon, Mar 20, 2017 at 01:38:49AM +0100, Michael Biebl wrote:
> Am 20.03.2017 um 01:36 schrieb Michael Biebl:
> > The relevant bits are in the journal log
> >> Mar 19 20:09:08 stretch systemd[1]: Stopped Login Service.
>
>
> Some of those in between
> > Mar 19 20:09:08 stretch dbus[451]: [system
On Sun, Mar 19, 2017 at 09:53:58PM +0100, Michael Biebl wrote:
> Since systemd starts everything in parallel, which service should
> ctrl+c apply to?
In this situation, systemd gives the distinct impression that all other
jobs have started, and it is now waiting for just one. A countdown timer
is
Just to confirm, things seem OK with the following in system.conf:
DefaultTimeoutStartSec=3s
DefaultTimeoutStopSec=15s
Everything including graphical desktop login comes up and down with no issues.
I think it'd be slightly better to keep the longer timeout, but allow the
console operator to inte
I think these messages are being (erroneously) passed specifically to
the KERN facility, not all facilities as the summary states.
For one thing, the superfluous messages don't appear in the user.log
file, as they do in kern.log, despite the fact that rsyslogd is
configured to route all facility=U
On Wed, Mar 29, 2017 at 06:35:35AM +0200, Michael Biebl wrote:
> Am 29.03.2017 um 06:03 schrieb Nathan Dorfman:
> > Package: systemd
> > Version: 232-19
> > Followup-For: Bug #848044
> >
> > Just tried a fresh install using the stretch rc2 amd64 netinst ISO,
&
Hi, this is still an issue with the default stretch install, if the
option to not set a root password is taken at installation.
It is quite severe IMO, especially considering how likely it is to be
discovered only when the rescue shell is actually needed.
If this really can't be fixed before rele
On Fri, Mar 31, 2017 at 12:51:08AM +0200, Michael Biebl wrote:
> Maybe I'm overly paranoid here, but maybe that helps to better
> understand my concerns.
No, your concerns sound reasonable to me, and I agree that demanding
a username from group sudo, along with its password sounds like it
could be
Control: retitle -1 systemd-logind: Unix group changes ignored by gdm/lightdm
until logind is restarted
On Fri, Mar 31, 2017 at 12:40:55PM +0200, Michael Biebl wrote:
> When you log out, do you still have an open logind session for that user
> (you can check that as root from the console via logi
