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

2015-08-16 Thread Harry Goldschmitt
On 8/12/15 7:22 PM, Chris Bell wrote:
> 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 kernel driver start up messages. Then the console
>> screen blanks for about 10 seconds. Then multi-user boot completes.
> The only other thing I can think of is when modesetting kicks in and is 
> configuring your graphics adapter? You could try adding the 'nomodeset' 
> kernel parameter to your boot, but keep in mind that you will lose 
> kernel modesetting, which could potentially cause issues with your 
> system. I'm not sure what else would cause the screen to 'blank' like 
> you are describing at that point in the boot.
>
> --Chris
>
I found it. Not a systemd issue at all. "console=ttyS0" had been dropped
from the kernel command line. Without it my Dell iDrac virtual console
went grey after GRUB boot. After I added the parameter the console 
stayed live and I could echo errors to /dev/tty1. I know everything I
need is available by journalctl, but the echos help when the system
doesn't come up far enough for journalctl to work.

Thanks for looking at this.

--
The information contained in this transmission may be confidential. Any 
disclosure, copying, or further distribution of confidential information is not 
permitted unless such privilege is explicitly granted in writing by Quantum. 
Quantum reserves the right to have electronic communications, including email 
and attachments, sent across its networks filtered through anti virus and spam 
software programs and retain such messages in order to comply with applicable 
data security and retention requirements. Quantum is not responsible for the 
proper and complete transmission of the substance of this communication or for 
any delay in its receipt.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


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 kernel driver start up messages. Then the console
screen blanks for about 10 seconds. Then multi-user boot completes.


The only other thing I can think of is when modesetting kicks in and is 
configuring your graphics adapter? You could try adding the 'nomodeset' 
kernel parameter to your boot, but keep in mind that you will lose 
kernel modesetting, which could potentially cause issues with your 
system. I'm not sure what else would cause the screen to 'blank' like 
you are describing at that point in the boot.


--Chris
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


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) foo.target.wants/foo.service
3) foo.service invokes /mydir/foo.sh
4) /mydir/foo.sh consists of
echo "foo.sh starting to sleep"
logger  "foo.sh starting to sleep"
sleep 10
echo "foo.sh after sleep"
logger "foo.sh after sleep"
systemctl isolate multi-user.target

What I see is a few kernel driver start up messages. Then the console screen 
blanks for about 10 seconds. Then multi-user boot completes. What I'm hoping to 
see is:
foo.sh starting to sleep
foo.sh after sleep

-Original Message-
From: systemd-devel [mailto:systemd-devel-boun...@lists.freedesktop.org] On 
Behalf Of Tomasz Torcz
Sent: Wednesday, August 12, 2015 12:26 PM
To: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] Console screen blanks while long running service 
executes

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 roll call of services running with [OK], etc. After 
> my service completes, the console comes back to life. My service uses 
> echo to output progress messages that show up in the journal. Is there 
> a way to keep the console from blanking?  >

  Put "consoleblank=0" in the kernel command line.

-- 
Tomasz Torcz   "Never underestimate the bandwidth of a station
xmpp: zdzich...@chrome.plwagon filled with backup tapes." -- Jim Gray

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_systemd-2Ddevel&d=BQIGaQ&c=8S5idjlO_n28Ko3lg6lskTMwneSC-WqZ5EBTEEvDlkg&r=naTX-IF7_QKyhqVve7SqbI_X3j-x4BDG1qRD3DBP5SU&m=U0VIxjS1yDAK5lMWm8xgxAd7UGv8CV6Jpj1MkgASCI8&s=8TInZVo_Ej5hIrZnvTp0PuR6KW_arTD2IcCCle4W3f4&e=
 

--
The information contained in this transmission may be confidential. Any 
disclosure, copying, or further distribution of confidential information is not 
permitted unless such privilege is explicitly granted in writing by Quantum. 
Quantum reserves the right to have electronic communications, including email 
and attachments, sent across its networks filtered through anti virus and spam 
software programs and retain such messages in order to comply with applicable 
data security and retention requirements. Quantum is not responsible for the 
proper and complete transmission of the substance of this communication or for 
any delay in its receipt.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


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 roll call
> of services running with [OK], etc. After my service completes, the console
> comes back to life. My service uses echo to output progress messages that show
> up in the journal. Is there a way to keep the console from blanking?  > 

  Put "consoleblank=0" in the kernel command line.

-- 
Tomasz Torcz   "Never underestimate the bandwidth of a station
xmpp: zdzich...@chrome.plwagon filled with backup tapes." -- Jim Gray

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


[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, the console 
comes back to life. My service uses echo to output progress messages that show 
up in the journal. Is there a way to keep the console from blanking?

--
The information contained in this transmission may be confidential. Any 
disclosure, copying, or further distribution of confidential information is not 
permitted unless such privilege is explicitly granted in writing by Quantum. 
Quantum reserves the right to have electronic communications, including email 
and attachments, sent across its networks filtered through anti virus and spam 
software programs and retain such messages in order to comply with applicable 
data security and retention requirements. Quantum is not responsible for the 
proper and complete transmission of the substance of this communication or for 
any delay in its receipt.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel