Migrating from openrc to systemd

Issues Related to Hardware (Sound, Video, Printers, Scanners, Webcams, Touchpads, Keyboards, Sensors, Drives, GRUB, etc.)

Moderator: Moderators

Migrating from openrc to systemd

Postby SabayonEncrypted » Sun Dec 29, 2013 13:54

My hardware:
Lenovo ThinkPad T61p, model 64608ZG

My goal:
Migration from openrc to systemd - Being able to have/use certain daemons/services under systemd as I was able to under openrc:
My readings:

My approach so far:
I started using 'eselect init set systemd' and 'systemctl enable kdm.service' as root.
Then I rebooted my system and noticed that quite a few services were not loaded by systemd. I added the missing ones using 'systemctl enable [name of the service].service' as root. And now I have
  • acpid
  • cpufrequtils
  • cups
  • gpm
  • tor
running after boot as before under openrc.
According to 'systemctl list-unit-files' there is no [name of the service].service file for
  • hdapsd
  • polipo
  • microcode_ctl
For hdapsd I already started an extra thread: https://forum.sabayon.org/viewtopic.php?f=56&t=31218

My remaining questions:
  1. Do I still need polipo for tor? If yes, how do I get this to work under systemd?
  2. How do I use or configure microcode_ctl as module for systemd?
  3. Any mistakes I made or anything I might have forgotton?
  4. How do I get rid of the errors shown in the systemd logs?
  5. What is NVRM trying to tell concerning nvidia and use of other console drivers? Is this relevant in some case?

Systemd log output concerning errors:
Code: Select all
# journalctl -b -p err
-- Logs begin at Mo 2013-12-23 08:31:54 CET, end at So 2013-12-29 13:29:06 CET. --
Dez 29 10:25:57 sabayon kernel: sd 6:0:0:0: [sdb] Asking for cache data failed
Dez 29 10:25:57 sabayon kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dez 29 10:25:57 sabayon kernel: sd 6:0:0:0: [sdb] Asking for cache data failed
Dez 29 10:25:57 sabayon kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dez 29 10:25:57 sabayon kernel: sd 6:0:0:0: [sdb] Asking for cache data failed
Dez 29 10:25:57 sabayon kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dez 29 10:26:08 sabayon /etc/init.d/net.eth0[5152]: net.eth0: not allowed to be hotplugged
Dez 29 10:26:08 sabayon /etc/init.d/net.wlan0[5154]: net.wlan0: not allowed to be hotplugged
Dez 29 10:26:14 sabayon avahi-daemon[5186]: chroot.c: open() failed: No such file or directory
Dez 29 10:28:15 endor pulseaudio[5500]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod:
Dez 29 10:28:29 endor hp-systray[5613]: hp-systray[5613]: error: option -s not recognized
Dez 29 10:28:35 endor pulseaudio[5642]: [pulseaudio] pid.c: Daemon already running.
Dez 29 10:28:35 endor pulseaudio[5648]: [pulseaudio] pid.c: Daemon already running.
Dez 29 10:50:01 endor /etc/init.d/syslog-ng[6294]: You are attempting to run an openrc service on a
Dez 29 10:50:01 endor /etc/init.d/syslog-ng[6295]: system which openrc did not boot.
Dez 29 10:50:01 endor /etc/init.d/syslog-ng[6296]: You may be inside a chroot or you may have used
Dez 29 10:50:01 endor /etc/init.d/syslog-ng[6297]: another initialization system to boot this system.
Dez 29 10:50:01 endor /etc/init.d/syslog-ng[6298]: In this situation, you will get unpredictable results!
Dez 29 10:50:01 endor /etc/init.d/syslog-ng[6300]: If you really want to do this, issue the following command:
Dez 29 10:50:01 endor /etc/init.d/syslog-ng[6301]: touch /run/openrc/softlevel
Dez 29 10:52:06 endor /etc/init.d/polipo[11189]: You are attempting to run an openrc service on a
Dez 29 10:52:06 endor /etc/init.d/polipo[11190]: system which openrc did not boot.
Dez 29 10:52:06 endor /etc/init.d/polipo[11191]: You may be inside a chroot or you may have used
Dez 29 10:52:06 endor /etc/init.d/polipo[11192]: another initialization system to boot this system.
Dez 29 10:52:06 endor /etc/init.d/polipo[11193]: In this situation, you will get unpredictable results!
Dez 29 10:52:06 endor /etc/init.d/polipo[11195]: If you really want to do this, issue the following command:
Dez 29 10:52:06 endor /etc/init.d/polipo[11196]: touch /run/openrc/softlevel


Systemd log output concerning acpi:
Code: Select all
# journalctl -b | grep acpi
Dez 29 10:25:57 sabayon kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Dez 29 10:25:57 sabayon kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Dez 29 10:25:57 sabayon kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Dez 29 10:25:57 sabayon kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Dez 29 10:25:57 sabayon kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Dez 29 10:25:57 sabayon kernel: acpi PNP0A08:00: Requesting ACPI _OSC control (0x1d)
Dez 29 10:25:57 sabayon kernel: acpi PNP0A08:00: ACPI _OSC control (0x1d) granted
Dez 29 10:25:57 sabayon kernel: acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
Dez 29 10:25:57 sabayon kernel: acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
Dez 29 10:25:57 sabayon kernel: Found 1 acpi root devices
Dez 29 10:25:57 sabayon kernel: acpi device:06: registered as cooling_device0
Dez 29 10:25:57 sabayon kernel: ACPI: Requesting acpi_cpufreq
Dez 29 10:25:57 sabayon kernel: ACPI: acpi_idle registered with cpuidle
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.24
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: http://ibm-acpi.sf.net/
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: ThinkPad BIOS 7LETC5WW (2.25 ), EC 7KHT24WW-1.08
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: Lenovo ThinkPad T61p, model 64608ZG
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: ACPI backlight control delay disabled
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: radio switch found; radios are enabled
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
Dez 29 10:26:00 sabayon kernel: thinkpad_acpi: Console audio control enabled, mode: monitor (read only)
Dez 29 10:26:00 sabayon kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input6
Dez 29 10:26:11 sabayon acpid[5203]: starting up with proc fs
Dez 29 10:26:14 sabayon acpid[5203]: 3 rules loaded
Dez 29 10:26:14 sabayon acpid[5203]: waiting for events: event logging is off
Dez 29 10:26:35 endor acpid[5203]: client connected from 5264[0:0]
Dez 29 10:26:35 endor acpid[5203]: 1 client rule loaded


Systemd log output concerning cpufrequtils:
Code: Select all
# journalctl -b | grep cpufreq
Dez 29 10:25:57 sabayon kernel: ACPI: Requesting acpi_cpufreq
Dez 29 10:26:08 sabayon systemd[1]: Starting CPU frequency scaling via cpufrequtils...
Dez 29 10:26:11 sabayon systemd[1]: Started CPU frequency scaling via cpufrequtils.
Dez 29 10:26:11 sabayon cpufrequtils-change.sh[5201]: cpufreq-set options:  --governor ondemand
Dez 29 10:26:11 sabayon cpufrequtils-change.sh[5201]: Governor options:


Systemd log output concerning gpm:
Code: Select all
# journalctl -b | grep gpm
Dez 29 10:26:08 sabayon /usr/sbin/gpm[5176]: *** info [daemon/startup.c(136)]:
Dez 29 10:26:08 sabayon /usr/sbin/gpm[5176]: Started gpm successfully. Entered daemon mode.


Systemd log output concerning tor:
Code: Select all
# journalctl -b | grep Tor
Dez 29 10:26:09 sabayon tor[5174]: Dec 29 10:26:09.767 [notice] Tor v0.2.5.1-alpha (git-e65b54ec75e3c9e9) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1e and Zlib 1.2.8.
Dez 29 10:26:09 sabayon tor[5174]: Dec 29 10:26:09.767 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Dez 29 10:26:09 sabayon tor[5174]: Dec 29 10:26:09.767 [notice] This version is not a stable Tor release. Expect more bugs than usual.
Dez 29 10:26:09 sabayon tor[5174]: Dec 29 10:26:09.785 [notice] Read configuration file "/etc/tor/torrc".
Dez 29 10:26:09 sabayon tor[5174]: Configuration was valid
Dez 29 10:26:11 sabayon tor[5209]: Dec 29 10:26:11.445 [notice] Tor v0.2.5.1-alpha (git-e65b54ec75e3c9e9) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1e and Zlib 1.2.8.
Dez 29 10:26:11 sabayon tor[5209]: Dec 29 10:26:11.446 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Dez 29 10:26:11 sabayon tor[5209]: Dec 29 10:26:11.446 [notice] This version is not a stable Tor release. Expect more bugs than usual.
Dez 29 10:26:11 sabayon tor[5209]: Dec 29 10:26:11.446 [notice] Read configuration file "/etc/tor/torrc".
Dez 29 10:26:11 sabayon tor[5209]: Dec 29 10:26:11.451 [notice] Opening Socks listener on 127.0.0.1:9050
Dez 29 10:26:12 sabayon Tor[5209]: Unable to open "/var/run/tor/tor.pid" for writing: No such file or directory
Dez 29 10:26:12 sabayon Tor[5209]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Dez 29 10:26:12 sabayon Tor[5209]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Dez 29 10:26:13 sabayon Tor[5209]: We now have enough directory information to build circuits.
Dez 29 10:26:13 sabayon Tor[5209]: Bootstrapped 80%: Connecting to the Tor network.
Dez 29 10:26:14 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 1; recommendation warn)
Dez 29 10:26:14 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 2; recommendation warn)
Dez 29 10:26:14 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 3; recommendation warn)
Dez 29 10:26:14 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 4; recommendation warn)
Dez 29 10:26:14 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 5; recommendation warn)
Dez 29 10:26:14 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 6; recommendation warn)
Dez 29 10:26:14 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 7; recommendation warn)
Dez 29 10:26:14 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 8; recommendation warn)
Dez 29 10:26:14 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 9; recommendation warn)
Dez 29 10:26:14 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 10; recommendation warn)
Dez 29 10:26:15 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 11; recommendation warn)
Dez 29 10:26:16 sabayon Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 12; recommendation warn)
Dez 29 10:26:35 endor Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 13; recommendation warn)
Dez 29 10:26:35 endor Tor[5209]: Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Network is unreachable; NOROUTE; count 14; recommendation warn)
Dez 29 10:26:45 endor Tor[5209]: Bootstrapped 85%: Finishing handshake with first hop.
Dez 29 10:26:46 endor Tor[5209]: Bootstrapped 90%: Establishing a Tor circuit.
Dez 29 10:26:47 endor Tor[5209]: Tor has successfully opened a circuit. Looks like client functionality is working.
Dez 29 10:26:47 endor Tor[5209]: Bootstrapped 100%: Done.


Systemd log output concerning polipo:
Code: Select all
# journalctl -b | grep polipo
Dez 29 10:52:05 endor run-crons[11166]: (root) CMD (/etc/cron.daily/polipo.sh)
Dez 29 10:52:06 endor /etc/init.d/polipo[11189]: You are attempting to run an openrc service on a
Dez 29 10:52:06 endor /etc/init.d/polipo[11190]: system which openrc did not boot.
Dez 29 10:52:06 endor /etc/init.d/polipo[11191]: You may be inside a chroot or you may have used
Dez 29 10:52:06 endor /etc/init.d/polipo[11192]: another initialization system to boot this system.
Dez 29 10:52:06 endor /etc/init.d/polipo[11193]: In this situation, you will get unpredictable results!
Dez 29 10:52:06 endor /etc/init.d/polipo[11195]: If you really want to do this, issue the following command:
Dez 29 10:52:06 endor /etc/init.d/polipo[11196]: touch /run/openrc/softlevel


Systemd log output concerning microcode:
Code: Select all
# journalctl -b | grep micro
Dez 29 10:26:04 sabayon kernel: microcode: CPU0 sig=0x6fb, pf=0x80, revision=0xb6
Dez 29 10:26:04 sabayon kernel: microcode: CPU0 sig=0x6fb, pf=0x80, revision=0xb6
Dez 29 10:26:04 sabayon kernel: microcode: CPU0 updated to revision 0xba, date = 2010-10-03
Dez 29 10:26:04 sabayon kernel: microcode: CPU1 sig=0x6fb, pf=0x80, revision=0xb6
Dez 29 10:26:04 sabayon kernel: microcode: CPU1 sig=0x6fb, pf=0x80, revision=0xb6
Dez 29 10:26:04 sabayon kernel: microcode: CPU1 updated to revision 0xba, date = 2010-10-03
Dez 29 10:26:04 sabayon kernel: microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba


Systemd log output concerning NVRM:
Code: Select all
# journalctl -b | grep NVRM
Dez 29 10:26:03 sabayon kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  331.20  Wed Oct 30 17:43:35 PDT 2013
Dez 29 10:26:08 sabayon kernel: NVRM: Your system is not currently configured to drive a VGA console
Dez 29 10:26:08 sabayon kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
Dez 29 10:26:08 sabayon kernel: NVRM: requires the use of a text-mode VGA console. Use of other console
Dez 29 10:26:08 sabayon kernel: NVRM: drivers including, but not limited to, vesafb, may result in
Dez 29 10:26:08 sabayon kernel: NVRM: corruption and stability problems, and is not supported.
SabayonEncrypted
Baby Hen
 
Posts: 12
Joined: Sat Mar 03, 2012 21:38

Re: Migrating from openrc to systemd

Postby Fitzcarraldo » Sun Dec 29, 2013 19:00

Don't use systemd myself, but perhaps the Arch Wiki article on Polipo would be of help (Arch Linux uses systemd): https://wiki.archlinux.org/index.php/Polipo
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7977
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: Migrating from openrc to systemd

Postby SabayonEncrypted » Mon Dec 30, 2013 10:26

To my first remaining question - a. Do I still need polipo for tor? - I have to say yes. Tor needs a proxy of some kind (from what I have understood after further readings).

The other question concerning polipo - a. If yes, how do I get this to work under systemd? - can't be answered by me for now. I tried what was given in the Arch Wiki without success:
Code: Select all
# systemctl restart polipo
Failed to issue method call: Unit polipo.service failed to load: Invalid argument. See system logs and 'systemctl status polipo.service' for details.
# systemctl status polipo.service
polipo.service
   Loaded: error (Reason: Invalid argument)
   Active: inactive (dead)

Dez 30 09:57:55 endor systemd[1]: [/etc/systemd/system/polipo.service:1] .include not allowed here. Ignoring.
Dez 30 09:57:55 endor systemd[1]: polipo.service lacks ExecStart setting. Refusing.
Dez 30 09:58:13 endor systemd[1]: [/etc/systemd/system/polipo.service:1] .include not allowed here. Ignoring.
Dez 30 09:58:13 endor systemd[1]: polipo.service lacks ExecStart setting. Refusing.


But instead of using polipo as a service with systemd I decided to use a script to start polipo directly whenever I want to use tor:
Code: Select all
# cat tor-start.sh
#!/bin/bash
#
# Shell-Skript zum Starten von Tor

echo -e " \033[1;32m*\033[0m Starte Polipo und anschließend die TOR-Oberfläche vidalia:";
echo "   polipo && vidalia"
/usr/bin/polipo &
sleep 2
vidalia &

This script works perfectly fine when used as root. I still have to sort out user rights and settings for my regular user. Vidalia log output shows:
Code: Select all
Dez 30 10:20:50.339 [Hinweis] Tor v0.2.5.1-alpha (git-e65b54ec75e3c9e9) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1e and Zlib 1.2.8.
Dez 30 10:20:50.339 [Hinweis] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Dez 30 10:20:50.339 [Hinweis] This version is not a stable Tor release. Expect more bugs than usual.
Dez 30 10:20:50.339 [Hinweis] Read configuration file "/home/.../.vidalia/torrc".
Dez 30 10:20:50.349 [Warnung] ControlPort is open, but no authentication method has been configured.  This means that any program on your computer can reconfigure your Tor.  That's bad!  You should upgrade your Tor controller as soon as possible.
Dez 30 10:20:50.349 [Hinweis] Opening Socks listener on 127.0.0.1:9050
Dez 30 10:20:50.349 [Hinweis] Opening Control listener on 127.0.0.1:9051
Dez 30 10:20:50.356 [Warnung] Error setting groups to gid 978: "Operation not permitted".
Dez 30 10:20:50.356 [Warnung] If you set the "User" option, you must start Tor as root.
Dez 30 10:20:50.357 [Warnung] Failed to parse/validate config: Problem with User value. See logs for details.
Dez 30 10:20:50.357 [Fehler] Reading config failed--see warnings above.


Every clue is welcome.
SabayonEncrypted
Baby Hen
 
Posts: 12
Joined: Sat Mar 03, 2012 21:38

Re: Migrating from openrc to systemd

Postby Cb7 » Mon Dec 30, 2013 11:48

A bit of explanations concerning polipo. TOR itself can be used as proxy, but only as (IIRC versions) SOCKS v4 and v5. Very often applications do not use SOCKS, and use HTTP proxy, which isn't by default supported by TOR. Polipo acts as a “middle man”, it receives connections for HTTP proxy and forwards them to TOR's SOCKS proxy.

So, if you have to use aplications that support only HTTP proxy with TOR, then polipo (or any other program acting like polipo) is required.

From brief look as Arch wiki, it seems that there's no proper unit file for polipo there. That's why there were errors in logs, there was no unit file that would say to systemd what to launch.
*sigh*
Usually when I don't have unit file, I just rip off it from other distro (usually Fedora, since they nicely support systemd), so here have one worth trying (it already has, what Arch wiki proposes):
Code: Select all
[Unit]
Description=A caching web proxy
Documentation=man:polipo(1) http://localhost:8123/

[Service]
Type=forking
User=polipo
Group=polipo
EnvironmentFile=/etc/sysconfig/polipo
ExecStart=/usr/bin/polipo -c $CONFIG
ExecReload=/usr/bin/kill -USR1 $MAINPID

[Install]
WantedBy=multi-user.target

I haven't tested it, since I don't use polipo. It may require a bit of adjusting, line “EnvironmentFile=/etc/sysconfig/polipo”, to point to your polipo config (I think it would be something like /etc/polipo.conf or /etc/polipo/soemthing.conf), though I'm not sure about that.


I'm not an expert, but logs concerning gpm look fine to me. If something with it doesn't work or doesn't behave as expected, could you elaborate?

TOR starts well, but perhaps you miss config for it… If you run tor as root/user, then config is stored in (IIRC) ~/.tor . To rightful place for system wide config for TOR is file /etc/tor/torrc .

About nvidia… Those errors probably will be there. nvidia doesn't care much, they have, from what I see, 1 way of doing things, any other way is unsupported. If you don't want errors concerning nvidia like that "forever", you could try using open source drivers, but then performance…

I don't know anything that could help with other things here, perhaps someone else will.
Why, and how to add "[Solved]" to your post. Please read. ← credits to Fitzcarraldo

Kind regards
~Zetok Zalbavar
Cb7
Growing Hen
 
Posts: 104
Joined: Sun Apr 07, 2013 7:13

Re: Migrating from openrc to systemd

Postby grimly64 » Mon Jan 20, 2014 2:28

For the NVRM: Nvidia error. Found this

https://bbs.archlinux.org/viewtopic.php?pid=1229168#p1229168

Particularly this:
hugogee wrote:Solved, thanks to the nice people in #archlinux

Add following to the end of kenel line in /boot/grub/grub.cfg

video=vesa:off vga=normal

e.g.
linux /vmlinuz-linux root=/dev/mapper/vgroup-root ro cryptdevice=/dev/sda2:vgroup quiet video=vesa:off vga=normal


Havn't tried this yet, (not at home)

Got this message after tying to convert to systemd and first reboot got the blinking cursor.
grimly64
Simple Hen
 
Posts: 43
Joined: Sun Apr 17, 2011 2:38

Re: Migrating from openrc to systemd

Postby batvink » Mon Jan 20, 2014 15:44

Microcode:
I believe you won't have to do anything.
Just first check "journalctl -xb | grep microcode" as root.

I made a microcode.service , but after starting the log said it was already started., and thus gave me a failed status.

The servicefile i used:
Create a new file in /etc/systemd/system (e.g. microcode.service) and add the following contents:
Code: Select all
[Unit]
Description=daemon to apply cpu microcode for Processor
ConditionFileIsExecutable=/etc/init.d/microcode_ctl

[Service]
Type=oneshot
ExecStart=/etc/init.d/microcode_ctl start
RemainAfterExit=yes

[Install]
WantedBy=local-fs.target
User avatar
batvink
Old Dear Hen
 
Posts: 495
Joined: Sun Oct 28, 2007 11:44
Location: the netherlands


Return to Hardware

Who is online

Users browsing this forum: No registered users and 7 guests