Re: [systemd-devel] How to debug why a unit is started when?

2018-03-16 Thread Andrei Borzenkov
16.03.2018 18:49, Paul Menzel пишет: > Dear systemd folks, > > > I am trying to get the GDM login screen started earlier on a Dell XPS 13 > 9370 with Debian Sid/unstable system with systemd 238. Currently, after > selecting the Linux kernel in GRUB it’s only displayed after roughly > eight to ten

Re: [systemd-devel] How to debug why a unit is started when?

2018-03-16 Thread Tomasz Torcz 👁️
On Fri, Mar 16, 2018 at 04:49:28PM +0100, Paul Menzel wrote: > Dear systemd folks, > > > I am trying to get the GDM login screen started earlier on a Dell XPS 13 > 9370 with Debian Sid/unstable system with systemd 238. Currently, after > selecting the Linux kernel in GRUB it’s only displayed afte

[systemd-devel] How to debug why a unit is started when?

2018-03-16 Thread Paul Menzel
Dear systemd folks, I am trying to get the GDM login screen started earlier on a Dell XPS 13 9370 with Debian Sid/unstable system with systemd 238. Currently, after selecting the Linux kernel in GRUB it’s only displayed after roughly eight to ten seconds while Linux takes around two seconds [

Re: [systemd-devel] safe and fast shutdown/reboot

2018-03-16 Thread Reindl Harald
Am 16.03.2018 um 11:36 schrieb prashantkumar dhotre: Thanks I understand that 'systemctl isolate other.target' will stop all present services and start services of other.target My thinking is : I can put all my apps in my.target and my.target can start after multi-user.target. that are all

Re: [systemd-devel] safe and fast shutdown/reboot

2018-03-16 Thread prashantkumar dhotre
Thanks I understand that 'systemctl isolate other.target' will stop all present services and start services of other.target My thinking is : I can put all my apps in my.target and my.target can start after multi-user.target. When shutting down , somewhere first i will do 'systemctl iso multi-user

Re: [systemd-devel] safe and fast shutdown/reboot

2018-03-16 Thread Andrei Borzenkov
16.03.2018 10:19, aleivag пишет: >> >> >> Won't work. Status changes only when job for a unit completes and jobs >> are executed in order of dependencies. Actually, jobs are *queued* in >> order of dependencies so nothing would indicate that you are going to >> shutdown until it is too late (i.e. a

Re: [systemd-devel] safe and fast shutdown/reboot

2018-03-16 Thread aleivag
> > > Won't work. Status changes only when job for a unit completes and jobs > are executed in order of dependencies. Actually, jobs are *queued* in > order of dependencies so nothing would indicate that you are going to > shutdown until it is too late (i.e. all normal services are stopped). > > ye