I find that I have :-

/usr/local/sbin/invoke-rc.d

which is dated Apr 2 2020.
I am trying to remember how it got there. I recall that I had been receiving "command not found" error messages.

I have been checking in my records, and I found it when I was trying OpenRC. At that time invoke-rc lived in /usr/sbin.

Geoff

Thank you!
I had, in fact, got ALWAYS_SET_PATH and ENV_SUPATH set up as above, but I was unable to open an X window. I then realised that it might be because I was using lxqt-sudo. On checking, I found that just using su did have $PATH set and I could open X programs. A quick check of the man page for lxqt-sudo showed that what I needed was the -s flag (for su rather than sudo).

Now when I run :-

lxqt-sudo -s rxvt -rv &

I have $PATH set and I can run X programs.
I run rxvt in reverse video so that I can easily spot that it is a root window.

Geoff

The latest version of config.auto steps through the database names in the various versions looking for the first one which is set to auto start.

# Automatically find the version and database name
# taken by postgresql/run

PGBINROOT="/usr/lib/postgresql"
RUNROOT="/var/run/postgresql"
CONFROOT="/etc/postgresql"

# Typical sort of values. I think "main" is the default name for a db.
# VERSION="13"
# DB="main"
# but we will look for the actual values in use.

# We look through the versions and then for each one, look through the db names
# stopping at the first one which is set to auto start in start.conf

start=''

get_db_name() {
    local c
    DB=''
    for c in "$CONFROOT"/"$VERSION"/*; do
	[ -e "$c"/postgresql.conf ] || continue

	DB=$(basename "$c")
        echo "$c ${VERSION} ${DB}"

        # evaluate start.conf, is it to be auto started?
	if [ -e "$c/start.conf" ]; then
	    start=$(sed 's/#.*$//; /^[[:space:]]*$/d; s/^\s*//; s/\s*$//' "$c/start.conf")
	else
	    start=auto
	fi
        echo "$c yields ${VERSION} ${DB} set to $start"

	[ "$start" = "auto" ] || continue

        # we have a db configured to auto start.

        return
    done
    # we have no valid database names in this version
    echo "Version $VERSION no database found set to auto start."
    DB=''
    return
}

get_version() {
    VERSION=''

    for ver in "$PGBINROOT"/* ; do
        VERSION=${ver##*/}
        echo "Version $VERSION."

        if [ -x "$PGBINROOT"/"$VERSION"/bin/pg_ctl ]; then

            # we have a valid version, now look through the db names
            get_db_name
            if [ -n "$DB" ] && [ "$start" = "auto" ]; then
                echo "$VERSION $DB $start"
                return
            fi
      	fi

    done
    # we have no valid databases to start
    echo "No databases set for auto start."
    VERSION=''
    DB=''
    exit 162
}

# Start here...

get_version

STATDIR="${RUNROOT}/${VERSION}-${DB}.pg_stat_tmp"

The very simple config.fixed script, sourced by the run script is

VERSION="15"
DB="main"

PGBINROOT="/usr/lib/postgresql"
RUNROOT="/var/run/postgresql"
CONFROOT="/etc/postgresql"
STATDIR="${RUNROOT}/${VERSION}-${DB}.pg_stat_tmp"

I have been thinking about how it might work with several Postgresql databases. I believe that each database would have its own service instance controlled by runit. This could be similar to having getty, where there are services called, e.g. getty-tty1, getty-tty2 etc.
I now have services called postgresql.a and postgresql.main. The contents of their directories are the same, apart for deleting the supervise links, so that they can be correctly recreated by update-service. The main run script still takes the config file, but config is now a link to one of several versions, config.fixed, config.auto and config.multi.

config.fixed simply sets the variables $VERSION and $DB along with the paths.
config.auto looks for the first $DB set for auto start, stepping through the ${VERSION}s.
config.multi gets the $DB from the service name extension and looks for the first $VERSION set for auto start.

I have also got the log/run script so that it picks up the service name and should not require changing.

In /etc/sv I have the service postgresql. It is necessary to copy over postgresql to postgresql.main and it should work! It is necessary to delete the supervise links and to change the config link over to config.multi.

cd /etc/sv
cp -a postgresql postgresql.main
cd postgresql.main
rm supervise
rm config
ln -s config.multi config
cd log
rm supervise

now remove the automatic set up and start the selective version :-

update-service --remove /etc/sv/postgresql
Service postgresql removed, the service daemon received the TERM and CONT signals.
sv status postgresql
fail: postgresql: unable to change to service directory: file does not exist
update-service --add /etc/sv/postgresql.main
Service postgresql.main added.
sv status postgresql.main
run: postgresql.main: (pid 4614) 4s; run: log: (pid 4613) 4s

cd /var/log/runit/postgresql.main
cat current 

For test purposes, I have the few files necessary to fool the scripts so that it will check the database "a" and find that it is set to be started manually, i.e. not run by runit. I have then set up postgresql.a in the same way as above. When the service postgresql.a was started it failed to find a database to start and looped about once a second. I have fixed this by adding the command

sv down /etc/sv/postgresql.a

which stops the looping, when no suitable database is found.

I will list the scripts in separate posts.

Thank you for the confirm-paste info. I had a quick look at rxvt-unicode using Synaptic and it does indeed list the file

amongst the installed files and this is confirmed with ls. I wonder whether this is new, as I have not noticed this effect before.

Thank you

Geoff

Thank you for that.

I also had to sort out the ownership of the files themselves, current and lock, but it is now running happily.

Someone here had worked out a run file that needed very little customisation between services, so my log/run file now looks like :-

#!/bin/sh

NAME=ssh
LOG="/var/log/runit/$NAME"
USER="_runit-log"
GROUP="adm"

chown "$USER:$GROUP" "$LOG"
chmod 750 "$LOG"

exec chpst -u "$USER" svlogd -tt "$LOG"

Maybe that should be 'chown -R "$USER:$GROUP" "$LOG"' to sort out the log files themselves, as well as the directory?

Geoff

Sorry, that should read button 1 and button 3 being pressed, when I press left & right simultaneously.

Thank you for the update on the theming!

I am running LXQt with Openbox and have set the overall theme to be Clearlooks-Phenix-Sapphire.

Geoff

Thank you for looking into this, Lorenzo.

My Chimaera installation is happy without runit starting a copy of dhclient, and having removed it from Daedalus, that also seems happy. So I would think that having it disabled-by-default is probably the correct thing to do.

I am not an expert in networking so I a not sure when we would need to run a copy of dhclient from the init system.

Geoff