Bug 43251

Summary:	systemd does not handle telinit right.
Product:	systemd	Reporter:	Kirill <kr404808>
Component:	general	Assignee:	Lennart Poettering <lennart>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	medium	CC:	evg, nathaniel.chen
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Kirill 2011-11-25 18:02:24 UTC

When in runlevel 3 I issue /sbin/telinit 5, instead of just starting xdm service, systemd restarts a lot of services that are already running, like network, and even worse - it closes all gettys, which makes this operation pretty painful.

Same with switching back to runlevel 5: instead of just stopping xdm service, systemd restarts a lot of services including network and getty.

It even does not really honors a lot of my settings: starts NetworkManager (why??? it is disabled), and few other things that are not supposed to run.

Switching back to sysV init fixed all my problems...

Comment 1 Lennart Poettering 2012-07-20 14:09:20 UTC

The getty issue should be fixed now, please test.

Comment 2 nchen 2013-03-05 21:40:50 UTC

Just tested with systemd 197 on Arch Linux, going from runlevel 3 to 5 didn't give me any network or getty issues, maybe this can be closed?

Comment 3 Kirill 2013-03-17 23:03:23 UTC

Can't confirm on SuSE 12.3 - now /sbin/telinit 3 just hangs with no response, until Ctrl+C. 

If I can't find a way to get rid of systemd in SuSE I will have to switch to another distribution :-(. That's a pity - I liked SuSE so far...

Comment 4 Cristian Rodríguez 2014-06-21 15:09:24 UTC

(In reply to comment #3)
> Can't confirm on SuSE 12.3 - now /sbin/telinit 3 just hangs with no
> response, until Ctrl+C. 
> 
> If I can't find a way to get rid of systemd in SuSE I will have to switch to
> another distribution :-(. That's a pity - I liked SuSE so far...


12.3 has systemd 195.. This issue is only corrected in version 197 or in openSUSE 13.1 ..

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.