I am trying to write an init script for gitea in alpine. The first code I tried was #!/sbin/openrc-run command=/usr/bin/gitea command_args="web" pidfile=/var/run/git.pid name="Gitea Daemon" description="Gitea - Git with a cup of tea" start() { ebegin "Starting Gitea" start-stop-daemon --start --exec /usr/bin/gitea \ --pidfile /var/run/git.pid eend $? } stop() { ebegin "Stopping Gitea" start-stop-daemon --stop --exec /usr/bin/gitea \ --pidfile /var/run/git.pid eend $? } Gitea does not fork, so when running above code, the service is starting and running but stays in foreground. So I tried to add --background option to start-stop-daemon. Now it is forking but the service is shown as „crashed“ although it’s running. I can fix this by manually creating a git.pid file, otherwise the service is unusable (won’t start nor stop) until I remove /var/run/openrc/started/git manually. When using the code above and calling it in background by rc-service git start & It will start gitea but rc-status shows the service as „starting“. Additionally I did not accomplish to log the output. Maybe somebody can give me a hint on this. I tried to add a redirect to command_args but this did not work and a redirect of start-stop-daemon’s output is useless when run in background.

I have a problem with hibernating my computer. Everything was working before an update. The update installed Plasma 6 and =x11-drivers/nvidia-drivers-550.127.05-r1. The kernel has not been updated. After the update, the following command does nothing: $ loginctl hibernate When I trace it using ltrace, I get the following output: $ ltrace loginctl hibernate setlocale(LC_ALL, "") = "C" elogind_set_program_name(0x7fffb8445a2d, 0x7f266b11bde0, 1, 0) = 0x7f266b135e08 log_setup(0x7fffb8445a2d, 0x7f266b11bde0, 1, 0) = 0 rlimit_nofile_bump(0x80000, 0x7fffb84452c0, 11, 0x7f266b0a9874) = 0 sigbus_install(0, 7, 0, 0x8000000000000000) = 0 getopt_long(2, 0x7fffb8445538, "hp:P:als:H:M:n:o:ci", 0x55aa2480b200, nil) = -1 bus_connect_transport(0, 0, 0, 0x7fffb84453e0) = 0 sd_bus_set_allow_interactive_authorization(0x55aa2482a2a0, 1, 128, 0x7f266b0a928b) = 0 dispatch_verb(2, 0x7fffb8445538, 0x55aa2480b560, 0x55aa2482a2a0 strcmp("halt", "hibernate") = -8 strcmp("poweroff", "hibernate") = 8 strcmp("reboot", "hibernate") = 10 strcmp("kexec", "hibernate") = 3 strcmp("suspend", "hibernate") = 11 strcmp("hibernate", "hibernate") = 0 geteuid() = 1000 on_tty(0x55aa248068c5, 0x7fffb8445a36, 0x55aa2482a2a0, 0x7f266b07986b) = 1 sd_bus_call_method(0x55aa2482a2a0, 0x55aa24806046, 0x55aa2480602e, 0x55aa24807968) = 0xffffff92 polkit_agent_open_if_enabled(0, 1, 0x55aa24808270, 785) = 0 log_get_max_level(5, 0, 0, 0x7f266b096094) = 6 sd_bus_call_method(0x55aa2482a2a0, 0x55aa24806046, 0x55aa2480602e, 0x55aa24807968) = 0xffffff92 log_get_max_level(0x55aa2482a010, 0x55aa2482cd40, 0, 785) = 6 memset(0x7fffb8444f90, '\0', 1024) = 0x7fffb8444f90 _bus_error_message(0x7fffb8444f70, 0xffffff92, 0x7fffb8444f90, 0x7fffb8444f90) = 0x7f266b13520d log_internal(3, 0xffffff92, 0x55aa24807b89, 366) = 0xffffff92 sd_bus_error_free(0x7fffb8444f70, 0x7fffb84443c0, 0, 0x7fffb8444f68) = 0 ) = 0xffffff92 polkit_agent_close(0x7fffb8444f70, 0x7fffb84443c0, 0, 0x7fffb8444f68 --- SIGCHLD (Child exited) --- ) = 0 strv_free(0, 0xfd6b, 0, 0x7f266b091343) = 0 sd_bus_flush_close_unref(0x55aa2482a2a0, 0xfd6b, 0, 0x7f266b091343) = 0 sd_notifyf(0, 0x55aa24806720, 110, 0x7f266b172b20) = 0 polkit_agent_close(0x55aa2482a010, 0x55aa2482bf80, 0x55af7e20817b, 33) = 0 pager_close(0, 0x55aa2482bf80, 0x55af7e20817b, 33) = 0 mac_selinux_finish(0, 0x55aa2482bf80, 0x55af7e20817b, 33) = 0 +++ exited (status 1) +++ Any idea where the problem might be? Everything was working before that update. Hibernating from the start menu doesn't work either. Syslog prints this: # grep loginctl /var/log/everything/current Nov 17 09:47:44 [loginctl] Failed to hibernate system via elogind: Connection timed out What currently goes wrong? The computer does not hibernate. **EDIT**: The command echo disk > /sys/power/state also does not hibernate, although cat /sys/power/state prints freeze mem disk.

I'm making my own service which communicates using sockets and SSL. It needs a certificate to work, but the certificate is currently locked behind a password. I can think of two ways to fix this. Either make the certificate not require a password. Or store the password to the certificate in a separate file, which the service can read in order to unlock the certificate. Both options feel like a bad idea. What is best practice here? Also, I'm using OpenRC not systemd.

Here is a gentoo-kernel(6.11.3) with openrc(0.55.1)+elogind(255.5) and dracut(103-r4)+grub(2.12-r5) operating system. plymouth version is 22.02.122-r2 Hardware: amd64, nvidia Plymouth can not work smoothly to start sddm with any graphic theme, configration wiht graphic theme will spalsh or flash the animation over and over again, but sddm is not be there as it should. Only "details" theme could work normally, but as you all known, this theme is not a graphic theme. I noticed that the publisher of Plymouth in gitlab announced that Plymouth do not support to build from source code, caused by it's relative to distro. And I noticed that current version of plymouth in gentoo repository with a timestamp in 2022, and current version in gitlab with timestamp 2024, I'm not sure whether what I'm encountered is relative to the version difference.

I want a specific service of OpenRC to run after my user login through agetty, LightDM (display manager), or any other way. This is because I have a emacs daemon running as OpenRC service for my specific user and I need this service to start only after a dbus session is created. One way to accomplish this is to run emacs daemon after dbus-launch [(related history)] runs my main session (currently XFCE session), which for instance happens after a login through the LightDM display manager . What I do as workaround is: restart emacs after login with my user to initialize correctly dbus integration with emacs. But this is just painful. There must be a better way to do that.

How do I find stdout of a process in openrc? Here's how I created my daemon. **/etc/init.d/mydaemon** #!/sbin/openrc-run command="python3" command_args="/srv/http/tornado.py" command_background="yes" pidfile="/tmp/tornado.pid" All I get in my logs is: * Starting tornado ... [ ok ] I have default /etc/rc.conf with set rc_logger="YES". What I would like to get is something like systemd allows to view stdout of a daemon with sudo journalctl -u mydaemon

I know that one can override dbus **session** services in ~/.local/share/dbus-1/services But it necessarily won't work for **system** services. **Under openrc**, I don't get systemd's systemctl command therefore : Is the quick and dirty (because service will be restored on next update) way consisting in renaming the associated service file in /usr/share/dbus-1/system-services, the only way to proceed ?

Gentoo, openrc, X11. Hi, For my suspend process, I need to get something like

[user] [DISPLAY]

for example:

chris :0

I can do it with:

for sessionid in $(/bin/loginctl list-sessions --no-legend | awk '{ print $1 }'); do
       /bin/loginctl show-session -p Display -p Name --value $sessionid | sed ':a;N;s/\n/ /'
done

BUT I need my script is used by root (suspend script in /etc/elogind/system-sleep/), and that's why I need to know user and display to use. And when used by root (script), /bin/loginctl list-sessions seems to not give any result. (used by root in a terminal works well) What is the best, robust way to achieve this please? Currently, I use:

if [ -S /tmp/.X11-unix/X* ] ; then
         display=":$(ls /tmp/.X11-unix/X* 2>/dev/null | sed 's#/tmp/.X11-unix/X##' | head -n 1)"
         if [ -n "$display" ]; then
                 user=$(who | grep '('$display')' | awk '{print $1}' | sort -u | head -n1)
                 [ -n "$user" ] && echo $user $display
         fi
fi

But I don't find it really very clean, even if it works very well for me.

I made a bit of research on the matter and also asked ChatGPT, but there doesn't seem to be a way to measure full boot time of an alpine distribution with OpenRC. Using dmesg, I can see the last message [ 0.689037] Run /sbin/init as init process But I want to know how much time it took to "complete" the init process. My use case is boot time sensitive, that's why I'm asking. Note I was able to boot an ubuntu 22.04 with systemd in 1s including kernel boot. In systemd, systemd-analyze is very useful. So I hope there is an equivalent (or a way) in openRC.

I would like to create a lightweight Linux distribution for my [Raspberry Pi 400](https://www.raspberrypi.com/products/raspberry-pi-400/) (for educational purposes). I have looked at [Buildroot](https://buildroot.org) and [Gentoo Linux](https://www.gentoo.org/) , but both require compiling OS components from scratch. How should I go about building a ROOTFS? I don't have much experience with bare-metal Linux... Ideally, I would: + Install the Kernel/[Firmware](https://github.com/raspberrypi/firmware) + Unpack the [Init System](https://github.com/OpenRC/openrc) + Get a [Package Manager](https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper) + Configure the system **Related:** https://unix.stackexchange.com/questions/87011/how-to-easily-build-your-own-linux-distro

I am trying to connect to my workplace's Office365 e-mail with Evolution mail and I am getting the following error when I try to authenticate: Failed to obtain access token from address “https://login.microsoftonline.com/common/oauth2/token” : Error calling StartServiceByName for org.freedesktop.secrets: Failed to activate service 'org.freedesktop.secrets': timed out (service_start_timeout=120000ms) When I try to connect to the mailbox in Evolution, a window pops up with my organization's authentication page; however, when I go through that I get the above error message. I am using Arch Linux and I have Gnome-Keyring installed; however, I am using OpenRC rather than systemd and I wonder if that might be part of the issue. Does anyone know what might be causing this and how I can connect to an Office365 mailbox with Evolution?

When I launch LibreOffice, I get the widget with the LibreOffice logo (the one displayed while the application loads), then my screen blinks three/four times, then it turns black. All I can do at that point is a hard reset and reboot. This is not a random event, it happens systematically, and only with LibreOffice. No error is displayed. The crash occurs with: - The default LibreOffice included in my distro. - With the LibreOffice binary downloaded from its website. - With the AppImage version downloaded from its website. These are my system details: - Laptop: Lenovo Thinkpad E585 (AMD Ryzen 2700). - Artix Linux - current version (= Arch without Systemd). - KDE - LibreOffice fresh (as of Nov 2022). - Init system: OpenRC. These are the files generated by LibreOffice in my home directory (~/.config/libreoffice/): https://drive.google.com/file/d/1TrNJe9L9V9PeqEgexFqXYRA_hUjf2rVe/view?usp=share_link

When I log in to XFCE, it seems /usr/lib/tumbler-1/tumblerd is started and uses relatively a large amount of memory. I do not need thumbnails. I want to remove it, but it is required for XFCE, so I cannot just uninstall the package. I tried [this existing answer on AskUbuntu](https://askubuntu.com/q/543494/470399) and disabled Thunar thumbnail/rc file and rebooted, but tumberd was still loaded when I log in. I thought of disabling the service, but I don't see a service with that name by doas rc-service --list when htop shows that tumblerd is running. Also, tumblerd seems to be terminated automatically after a while, so maybe it is not an always-running service. I checked [the package's files](https://pkgs.alpinelinux.org/contents?branch=v3.16&name=tumbler&arch=x86_64&repo=community) . What I saw was "dbus-1/service" like the following. Are they different from regular services? How can I stop it from getting loaded? * /usr/share/dbus-1/services/org.xfce.Tumbler.Cache1.service * /usr/share/dbus-1/services/org.xfce.Tumbler.Manager1.service * /usr/share/dbus-1/services/org.xfce.Tumbler.Thumbnailer1.service

I've got some issue with gentoo rc-status (currently using sys-apps/openrc-0.45.2-r1 but it was happening long time before this version). From time to time some of machines are loosing ip_forwarding. I've narrowed it to running rc-status right now. # cat /proc/sys/net/ipv4/ip_forward; rc-status; cat /proc/sys/net/ipv4/ip_forward 1 * Caching service dependencies ... [ ok ] Runlevel: default [SOME SERVICES LISTED HERE] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed/wanted Dynamic Runlevel: manual [SOME SERVICES LISTED HERE] 0 What could be possible reason behind this logic of this tricky changing of ip_forwarding state? Also this happens from time to time. I need to wait a couple of days / weeks before another rc-status takes down ip_forwarding. Key difference here is that Caching service dependencies ... [ ok ] does not appear when ip_forwarding is not touched.

Here is my incrontab (tony's incrontab): /home/tony/Workspace/cocoonr/ui/static/ui/img/icons/vector IN_MODIFY,IN_CREATE,IN_MOVED_TO /bin/sh /home/tony/Workspace/cocoonr/boilerplate/svg2djangohtml $@/$# /home/tony/Workspace/cocoonr/ui/templates/inc/icons/ I tested it multiple times changing some things, no way to make it work when incrond is run as a service (using openrc). If I run incrond in foreground (incrond -n), then tony's incrontab works If I set root's incrontab to the one given above, it works even when run as a service. My tony is in /etc/incron.allow: root tony And there is no /etc/incron.deny. I even tried with a much simpler incrontab: /tmp/foo IN_ATTRIB touch /tmp/bar The results are the same. How to make user's incrontab working?

I use Alpine Linux and podman command to generate container systemd
**Command:**

podman generate systemd -n test -f

**Output:**

# container-test
# autogenerated by Podman 3.4.7
# Fri Apr 29 02:29:47 CEST 2022

[Unit]
Description=Podman container-test.service
Documentation=man:podman-generate-systemd(1)
Wants=network-online.target
After=network-online.target
RequiresMountsFor=/run/containers/storage

[Service]
Environment=PODMAN_SYSTEMD_UNIT=%n
Restart=on-failure
TimeoutStopSec=70
ExecStart=/usr/bin/podman start test
ExecStop=/usr/bin/podman stop -t 10 test
ExecStopPost=/usr/bin/podman stop -t 10 test
PIDFile=/run/containers/storage/overlay-containers/fc64dadf99ddb38f98ddcb3e022bc575ca39cd57f4e2e8c5cc63595377e2c3ad/userdata/conmon.pid
Type=forking

[Install]
WantedBy=default.target

Because Alpine Linux is not using systemd I need to convert this container service to openrc **The Goal is:**
to start specific containers as as service and this containers must be visible to root only

I switched recently to Artix Linux with OpenRC as Init-system. I was using Manjaro before, which uses Systemd. Anyway, I was trying to install some packages I used on Manjaro that I have gotten from the snap-store. But I couldn't install it because of some systemd dependency. I think was trying to onlyOffice and other stuff.

I have a service called xboxdrvd that is triggered (and only activated/deactivated) by a [udev](https://github.com/ryukinix/xboxdrv-bin/blob/master/61-twin-joystick.rules) rule, however always calling rc-status I got that the service was started on "manual" runlevel:  The hotplugged is not for that type of events? I did read the [gentoo docs], but there is not so much thing on there.

I am using Gentoo as Host OS for Docker containers. I have compiled kernel using instructions on page https://wiki.gentoo.org/wiki/Docker#Kernel and I have installed Docker from Gentoo repository. Host system informations: pecan@tux ~ $ uname -a Linux tux 4.12.12-gentoo #8 SMP Sat Oct 7 13:58:47 CEST 2017 x86_64 Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz GenuineIntel GNU/Linux Docker version: pecan@tux ~ $ docker version Client: Version: 17.03.2-ce API version: 1.27 Go version: go1.9.1 Git commit: f5ec1e2 Built: Sat Oct 7 14:50:59 2017 OS/Arch: linux/amd64 Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Look at "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?". The same message appears if I try get docker system-wide informations: pecan@tux ~ $ docker info Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? The same error appears if I try run the same command as sudo, so this error applies to daemon. I tried to check if there a mistake in Docker daemon privileges. pecan@tux ~ $ sudo docker info Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Based on the message I am able to say that maybe Docker daemon not running. I checked daemon status to make sure: pecan@tux ~ $ sudo service docker status * status: crashed Docker daemon is crashed. To see the reason, I looked at the logs: pecan@tux ~ $ cat /var/log/docker.log time="2017-10-07T14:52:13.178261811+02:00" level=info msg="libcontainerd: new containerd process, pid: 32311" time="2017-10-07T14:52:14.434232306+02:00" level=info msg="Graph migration to content-addressability took 0.00 seconds" time="2017-10-07T14:52:14.434413425+02:00" level=warning msg="Your kernel does not support cgroup blkio weight" time="2017-10-07T14:52:14.434423960+02:00" level=warning msg="Your kernel does not support cgroup blkio weight_device" time="2017-10-07T14:52:14.434759986+02:00" level=info msg="Loading containers: start." time="2017-10-07T14:52:14.437180876+02:00" level=info msg="Firewalld running: false" Error starting daemon: Error initializing network controller: list bridge addresses failed: no available network Currently, that is a point in that I do not know what should I do to be able run Docker daemon. Useful informations: - I am connected to OpenVPN through UDP. - I have disabled iptables and ip6tables. - I have set 8.8.8.8 and 8.8.4.4 DNS providers. - I have running privoxy and tor daemons. - I use OpenRC init system. Can you help me?

some time ago I moved from Systemd to OpenRC. It was very different, to be able to use audio and webcam I had to add my user to the audio, optical and video group. As some software uses pkexec to be run as superuser, when I opened them (Because I use XFCE) nothing happened. When I used Systemd this didn´t happened, and it´s configured to use /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 (which I have it installed). When I write pkexec in a terminal this is the output $ pkexec ==== AUTHENTICATING FOR org.freedesktop.policykit.exec === Authentication is required to modify fingerprint authentication data Authenticating as: (MY USERNAME) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie ==== AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. I don´t know how to enable the polkit daemon/service in OpenRC, in Systemd the service it´s named "polkit". But there is ConsoleKit (what´s the difference?) which is seems to fail $ service consolekit status * status: stopped # service consolekit restart * starting consolekit . . $ service consolekit status * status: crashed My distro is Parabola (Arch Based, with the difference that is removes all the nonfree packages from the repo & Arch itself, as Arch uses Systemd, Parabola too) and I changed to OpenRC in a virtual machine, and I am testing it. Thanks in advance Other outputs $ groups wheel network video audio storage polkitd $USERNAME