Feature Request #2783

guix does not work with openrc after migration from systemd

jgart - almost 4 years ago - . Updated almost 4 years ago.

% Done:




I migrated over to openrc and I can't run the guix daemon now because it was dependent on systemctl. How should I migrate guix over to openrc? Should I just create an init script or is there more I should be configuring? Any help is greatly appreciated!



Updated by bill-auger almost 4 years ago

it probably just needs some init scripts - surely you could
start it manually - i dont suppose that guix actually depends on


Updated by jgart almost 4 years ago

I was able to start guix manually with the following command:

~ $ sudo /var/guix/profiles/per-user/root/current-guix/bin/guix-daemon --build-users-group=guixbuild
[sudo] password for jgart:
guile: warning: failed to install locale

accepted connection from pid 9654, user jgart

Should I reopen this as a feature request for adding an openrc init script to the guix packaged in the parabola repositories?

The version that is currently packaged here looks like it only supports a system running systemd.

I imagine we would have to update that package to the current version and also add an init script for openrc.

Should there be a guix-openrc and a guix-systemd in the parabola repositories or should it be just be one package that asks the user which init script they want when installing via pacman?


Updated by jgart almost 4 years ago

I was able to register this openrc init file for guix-daemon successfully:

#! /sbin/openrc-run

description="guix build daemon"

It is a modification of this:

I couldn't get the localstatedir syntax to run successfully in Vincent's code. The above works for me for now.

The following commands work as expected now on parabola:

sudo rc-update add guix-daemon
sudo rc-service guix-daemon start
sudo rc-service guix-daemon start

If anybody has suggestions and incites about this it would be greatly appreciated.


Updated by bill-auger almost 4 years ago

jgart -

this ticket is already set as a 'feature-request' - nothing more
need to happen until it is done

if there is a patch upstream, the best thing to do is to simply
wait to see if it is accepted - then the next release will have

my suggestion is the same as yesterday - if you would like to
help get the next release out; write to the mailing list so that
people will know, and perhaps offer advice - GNUtoo asked me
about this today, and he knows what needs to be done; but you
were not in the IRC channel at the time, so nothing happened - a
discussion on the mailing list would be the best way to get
things in motion

Also available in: Atom PDF