A few days ago I installed systemd (version 204-6) and am experiencing some problems.
Firstly the lack of networking when in multi-user.target. Is there a fix for the this?
For example, at present, when doing a du I switch to multi-user (used to be init 3) with
systemctl isolate multi-user.target
I then have to do
ifup etho
to enable the the connection so that the du can proceed because neither
systemctl start network.service
nor
systemclt start ifplugd.service
seem to achieve a connection.
Secondly dropping to the terminal via CRTL-ALT-F1 loses previously configured terminal parameters eg. keyboard rate and delay are ignored. This is particularly annoying as the default key repeat rate is too fast for me.
I've looked in the files in /lib/systemd/system but as I'm new to systemd I'm reluctant to attempt any remedial modifications.
So is anyone sharing my problems or know of fixes for the them?
Quote from: clubex on 2014/01/12, 17:57:30
A few days ago I installed systemd (version 204-6) and am experiencing some problems.
Firstly the lack of networking when in multi-user.target. Is there a fix for the this?
For example, at present, when doing a du I switch to multi-user (used to be init 3) with
systemctl isolate multi-user.target
I then have to do
ifup etho
to enable the the connection so that the du can proceed because neither
systemctl start network.service
nor
systemclt start ifplugd.service
seem to achieve a connection.
Secondly dropping to the terminal via CRTL-ALT-F1 loses previously configured terminal parameters eg. keyboard rate and delay are ignored. This is particularly annoying as the default key repeat rate is too fast for me.
I've looked in the files in /lib/systemd/system but as I'm new to systemd I'm reluctant to attempt any remedial modifications.
So is anyone sharing my problems or know of fixes for the them?
http://forum.siduction.org/index.php?topic=4189.msg35145;topicseen#msg35145
So the issue remains?
systemctl isolate multi-user.target
should move to a networking level but dosen't.
Does this also occur with the December 2013 release?
By the way KDM is my dm.
I use "systemctl stop kdm", it allows the network to stay enabled. The multi-user.target always disabled the network for me.
Edit: dibl has a thread nearby that discusses the use of multi-user.target and using systemctl stop ?dm. You can read it here: http://forum.siduction.org/index.php?topic=4189.msg35171#msg35171
Quote from: GoinEasy9 on 2014/01/14, 05:08:07
I use "systemctl stop kdm", it allows the network to stay enabled. The multi-user.target always disabled the network for me.
I use
systemctl isolate runlevel3.target
this works just fine.
Quote from: OppaErich on 2014/01/14, 08:15:15
Quote from: GoinEasy9 on 2014/01/14, 05:08:07
I use "systemctl stop kdm", it allows the network to stay enabled. The multi-user.target always disabled the network for me.
I use
systemctl isolate runlevel3.target
this works just fine.
That would be the third Command for the same concern... ::)
Thanks guys.
systemctl isolate runlevel3.target
doesn't work for me. Networking still goes down.
But stopping the dm
systemctl stop kdm.target
keeps networking up.
That said this is only a work-a-round. A I undestand it multi-user.target on Debian is supposed to be the equivalent of switching to runlevel 3 using init 3 but it clearly isn't. System wise this is pretty basic stuff and shouldn't be an issue. As it occurs with both lightdm and kdm it's either a systemd bug or a change in Debian policy. I seriously doubt it's the latter.
Also having to slow the keyboard rate every time I drop to tty is a real PITA.
Maybe everything functions correctly on the December 2013 issue of siduction. I'll give it a go when I can spare the time.
So far my experience of converting my rolling release of siduction from sysvinit to systemd hasn't inspired much confidence although what does work I like; especially the notion of config files rather than scripts.