Bug 1477207

Summary:	rlogin killed when changing run level
Product:	Red Hat Enterprise Linux 7	Reporter:	James Pearson <james-p>
Component:	rsh	Assignee:	Michal Ruprich <mruprich>
Status:	CLOSED ERRATA	QA Contact:	Ondrej Mejzlik <omejzlik>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.3	CC:	omejzlik, psklenar, thozza
Target Milestone:	rc	Keywords:	FastFix
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	rsh-0.17-79.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-30 08:00:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description James Pearson 2017-08-01 13:21:00 UTC

Description of problem:

If the runlevel on a host is changed, any rlogin sessions to that host are killed

Version-Release number of selected component (if applicable):

rsh-server-0.17-76.el7_1.1.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Install rsh-server on host
2. rlogin into host from a client
3. On rsh-server host, change run level (e.g. with 'telinit' or 'systemctl isolate'

Actual results:

rlogin session terminates

Expected results:

rlogin session continues

Additional info:

Adding 'KillMode=none' to the '[Service]' section of rlogin@.sevice prevents the session from being killed - although not sure if this is a sensible workaround?

Comment 2 Michal Ruprich 2017-08-08 15:23:21 UTC

The KillMode=none option could actually make some trouble during shutdown. The option we're looking for here is IgnoreOnIsolate=true in the [Unit] section. I tried that and it works. 

James can you confirm that adding this option to rlogin@.service works for you as well? If so, I will probably add this to the service file.

Regards,
Michal

Comment 3 James Pearson 2017-08-08 15:41:24 UTC

IgnoreOnIsolate=true appears to work for me - thanks

Comment 5 James Pearson 2018-02-07 16:38:35 UTC

Is this likely to be fixed in 7.5 ?

Comment 12 errata-xmlrpc 2018-10-30 08:00:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3057