Re: [systemd-devel] Console screen blanks while long running service executes

2015-08-12 Thread Chris Bell
On 2015-08-12 20:19, Harry Goldschmitt wrote: I just modified my grub kernel command line to add the consoleblank=0 parameter. That isn't the problem. First consoleblank is the kernel screensaver and according to the documentation it kicks in after 15 minutes by default. What I see is a few kern

Re: [systemd-devel] Console screen blanks while long running service executes

2015-08-12 Thread Harry Goldschmitt
I just modified my grub kernel command line to add the consoleblank=0 parameter. That isn't the problem. First consoleblank is the kernel screensaver and according to the documentation it kicks in after 15 minutes by default. What I'm doing for testing is: 1) systemctl set-default foo.target 2)

Re: [systemd-devel] Method to Wait for service to complete

2015-08-12 Thread killermoehre
Am 12.08.2015 um 20:34 schrieb Harry Goldschmitt: > I have a service that has to complete before boot can continue. Is there > an “approved” method for doing this? > > > > I have an ugly solution I’ve come up with… I’ve created a foo.target to > run my foo.service and set the default.target to

Re: [systemd-devel] Console screen blanks while long running service executes

2015-08-12 Thread Tomasz Torcz
On Wed, Aug 12, 2015 at 06:41:35PM +, Harry Goldschmitt wrote: > I have a target that runs a service during boot on CentOS 7.1. The service > takes a minimum of 30 sec. to run and a maximum of 15 min. While it's running, > the console screen blanks. Before my service runs I see the expected rol

[systemd-devel] Method to Wait for service to complete

2015-08-12 Thread Harry Goldschmitt
I have a service that has to complete before boot can continue. Is there an "approved" method for doing this? I have an ugly solution I've come up with... I've created a foo.target to run my foo.service and set the default.target to my foo.target. After my foo.service completes, I'm issuing "sy

[systemd-devel] Console screen blanks while long running service executes

2015-08-12 Thread Harry Goldschmitt
I have a target that runs a service during boot on CentOS 7.1. The service takes a minimum of 30 sec. to run and a maximum of 15 min. While it's running, the console screen blanks. Before my service runs I see the expected roll call of services running with [OK], etc. After my service completes,

Re: [systemd-devel] Kill on console works, ExecStop not

2015-08-12 Thread Colin Guthrie
Florian Lindner wrote on 12/08/15 15:47: > Hello, > > I have a systemd 224 user service unit that starts the emacs daemon: > > [Unit] > Description=Emacs: the extensible, self-documenting text editor > > [Service] > Type=forking > ExecStart=/usr/bin/emacs --daemon > ExecStop=/usr/bin/emacsclient

[systemd-devel] Kill on console works, ExecStop not

2015-08-12 Thread Florian Lindner
Hello, I have a systemd 224 user service unit that starts the emacs daemon: [Unit] Description=Emacs: the extensible, self-documenting text editor [Service] Type=forking ExecStart=/usr/bin/emacs --daemon ExecStop=/usr/bin/emacsclient --eval "(progn (setq kill-emacs-hook nil) (kill-emacs))" Rest