Summary: | sys-process/runit-2.1.2-r1: several issues with ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Efros <powerman-asdf> |
Component: | Current packages | Assignee: | William Hubbs <williamh> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | aranea, base-system |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | runit-2.1.2-r1.ebuild.patch |
Description
Alex Efros
2017-03-06 05:04:31 UTC
I'm looking at this today. It looks like the best way forward is going to be to separate the boot scripts into their own package, so you will have runit then runit-openrc or something similar. It looks like /etc/runit/2 and /etc/runit/ctrlaltdel can stay with runit, because they should be the same regardless of how you boot your system, But /etc/runit/1 and /etc/runit/3 will need to be able to be customized easily, along with the contents of /etc/runit/runsvdir and /etc/service. (In reply to William Hubbs from comment #2) > It looks like /etc/runit/2 and /etc/runit/ctrlaltdel can stay with > runit, because they should be the same regardless of how you boot your > system, But /etc/runit/1 and /etc/runit/3 will need to be able to be > customized easily, along with the contents of /etc/runit/runsvdir and > /etc/service. Yes, but it's unlikely makes sense to split these files into different packages just because of this. Also, sometimes /etc/runit/2 also needs some modifications, for example here is mine: --- #!/bin/bash PATH=/command:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin exec 3<>/var/log/all/.log exec &>/var/log/all/.log exec env - PATH=$PATH \ runsvdir -P /etc/service 'log: ...........................................................................................................................................................................................................................................................................................................................................................................................................' --- It looks this way because I'm using chain of log-services: - most services write logs to their own svlogd, as usually - some config files of these svlogd for some services are configured to duplicate some lines to svlogd's STDERR - ./log/run which runs svlogd is configured to redirect svlogd's STDERR to /var/log/all/.log (which is a named PIPE file created with `mkfifo`) - there is /etc/service/log-all/ service which runs svlogd reading from /var/log/all/.log and writing logs into /var/log/all/current This way I've most interesting log lines from all services in one log file, which is usually always open with `tail -F`. (Also this log is used to implement desktop notifications for most critical events with help of another one service.) So, just like I've redirected STDERR of all svlogd of all services I've also redirected there STDERR of runsvdir itself, to see in this log messages which wasn't properly redirected in some service's ./run files. *** Bug 632174 has been marked as a duplicate of this bug. *** runit-2.1.2-r1 doesn't start: "start-stop-daemon: /usr/bin/runsvdir does not exist" it's because of wrong path in /etc/init.d/runsvdir: "command=/usr/bin/runsvdir" while actual path is /bin/runsvdir |