Bug 627020

Summary:	systemd "translations" of respawn property are missing
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-24 23:56:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2010-08-24 21:23:17 UTC

Description of problem:

It appears that 'respawn' line from /etc/init/tty.conf is "translated" to
Restart=restart-always
RestartSec=0
in /etc/systemd/system/getty.target.wants/getty@tty?.service files. A similar line from /etc/init/prefdm.conf is left out in /etc/systemd/system/graphical.target.wants/prefdm.service with this effect that killing gdm leaves a black screen instead of a restart (I am not sure how
"respawn limit 10 120" should be handled).

Another file with 'respawn' is /etc/init/serial.conf and apparently an equivalent of that is entirely missing from /etc/systemd/ while on various occasions a serial console is indispensable.

Version-Release number of selected component (if applicable):
systemd-7-3.fc14.x86_64

How reproducible:
always

Additional info:
Booting with "init=/sbin/upstart" restores the previous behaviour

Comment 1 Michal Schmidt 2010-08-24 23:40:26 UTC

steps to reproduce:
1. boot into graphical.target
2. login
3. su -c "killall gdm-binary"

actual result:
a black screen

expected result:
respawned gdm

Comment 2 Lennart Poettering 2010-08-24 23:56:35 UTC

Fixed now upstream.

There's no equivalent to "respawn limit 10 120" as we have an implicit respawn rate limiting always enabled which you cannot disable. We might make that configurable later on, but I am not sure this would really be a good idea.

Comment 3 Michal Jaegermann 2010-08-25 00:21:41 UTC

(In reply to comment #2)
> Fixed now upstream.

Thanks!

> There's no equivalent to "respawn limit 10 120" as we have an implicit respawn
> rate limiting always enabled which you cannot disable.

That is what roughly I hoped for but I was not sure.

What about a serial console issue before it will get lost?  When it is needed it is usually **really needed**.  There are USB adapters if a real serial port hardware is not available.