You are not logged in.

#1 2012-08-04 11:02:19

ichi-no-eda
Member
Registered: 2011-08-28
Posts: 33

[solved] systemd - problems transitioning from initscripts

Hi there.

I'd like to transition from initscripts, sysvinit to systemd.
I followed this Arch wiki: http://wiki.archlinux.org/index.php/Systemd and wanted to carry out a pure systemd installation.

- So I installed systemd, systemd-sysvcompat, systemd-arch-units.
- Then added the kernel parameters and did grub-mkconfig -o /boot/grub/grub.cfg.
- Created the systemd config files /etc/hostname, /etc/vconsole.conf, /etc/locale.conf, /etc/timezone with the appropriate entries.

The problem is step 4.:
I had 9 daemons started in /etc/conf: alsa, crond, dbus, network, preload, sensors, slim, syslog-ng and ufw.

When I do:

systemctl enable crond.service

I get:

Operation failed: No such file or directory

This happens whith any other service too.

What files or directories are missing here? How can I add them?

Also:

systemctl

results in:

Failed to get D-Bus connection: No connection to service manager.

Last edited by ichi-no-eda (2012-08-04 11:42:17)

Offline

#2 2012-08-04 11:28:58

graysky
Member
From: The worse toilet in Scotland
Registered: 2008-12-01
Posts: 8,821
Website

Re: [solved] systemd - problems transitioning from initscripts

If you're using the Arch defaults, then you are using cronie, not crond.  I don't believe there is a crond.service file.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#3 2012-08-04 11:33:29

ichi-no-eda
Member
Registered: 2011-08-28
Posts: 33

Re: [solved] systemd - problems transitioning from initscripts

Yeah. Found it too. https://wiki.archlinux.org/index.php/Systemd says:

If <service_name>.service does not exist:

- the service file may not be available for systemd. In that case, you'll need to keep rc.conf to start the service during boot up.

- systemd may name services differently, e.g. cronie.service replaces crond init daemon; alsa-store.service and alsa-restore.service replace the alsa init daemon. Another important instance is the network daemon, which is replaced with another set of service files

The service files can be found here:

/usr/lib/systemd/system/

Last edited by ichi-no-eda (2012-08-04 11:41:53)

Offline

#4 2012-08-04 11:48:05

progandy
Member
Registered: 2012-05-17
Posts: 2,152

Re: [solved] systemd - problems transitioning from initscripts

ichi-no-eda wrote:

The service files can be found here:

/usr/lib/systemd/system/

You can get a list with "systemctl list-unit-files", too.

Also:
systemctl
results in:
Failed to get D-Bus connection: No connection to service manager.

You need to boot with systemd instead of sysvinit first.

Last edited by progandy (2012-08-04 11:49:28)

Offline

Board footer

Powered by FluxBB