You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Android 7, When running the following daemonize command runsvdir will fail. daemonize -l $PREFIX/var/run/runsvdir.lock -p $PREFIX/var/run/runsvdir.pid $PREFIX/bin/applets/runsvdir /data/data/com.termux/files/home/.sv
After a lot of testing I finally figured out the problem: Everything daemonize executes is run from the / directory (that's why it needs absolute paths). Starting with Android 7 / no longer has read permissions.
$ ls /
ls: cannot open directory '/': Permission denied
runsvdir, for some reason, needs read access to the current working directory.
Workaround
Specifing the working directory for daemonize fixes the problem daemonize -c $PREFIX -l $PREFIX/var/run/runsvdir.lock -p $PREFIX/var/run/runsvdir.pid $PREFIX/bin/applets/runsvdir /data/data/com.termux/files/home/.sv
Perhaps daemonize could be patched to set the default working directory to $PREFIX
The text was updated successfully, but these errors were encountered:
Since an update, service-daemon refuses to start, it seems necessary to manually
specify the working directory of start-stop-daemon to avoid permission errors.
This issue seems to be related to this one:
termux/termux-packages#614
Since an update, service-daemon refuses to start, it seems necessary to manually
specify the working directory of start-stop-daemon to avoid permission errors.
This issue seems to be related to this one:
termux/termux-packages#614
ghost
locked and limited conversation to collaborators
Oct 9, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On Android 7, When running the following daemonize command runsvdir will fail.
daemonize -l $PREFIX/var/run/runsvdir.lock -p $PREFIX/var/run/runsvdir.pid $PREFIX/bin/applets/runsvdir /data/data/com.termux/files/home/.sv
Checking the logs reveals the following problem:
After a lot of testing I finally figured out the problem: Everything daemonize executes is run from the
/
directory (that's why it needs absolute paths). Starting with Android 7/
no longer has read permissions.runsvdir, for some reason, needs read access to the current working directory.
Workaround
Specifing the working directory for daemonize fixes the problem
daemonize -c $PREFIX -l $PREFIX/var/run/runsvdir.lock -p $PREFIX/var/run/runsvdir.pid $PREFIX/bin/applets/runsvdir /data/data/com.termux/files/home/.sv
Perhaps daemonize could be patched to set the default working directory to $PREFIX
The text was updated successfully, but these errors were encountered: