mirror
/
Jackett
mirror of https://github.com/Jackett/Jackett
1
0
Fork 0
Code Issues Releases Wiki Activity
Jackett/jackett_launcher.sh

19 lines
402 B
Bash
Raw Normal View History

jackett_launcher.sh fine tuning (#6297) + Execute script with system default bourne shell. On Debian this is "dash" by default, which has a much lower memory foot print compared to bash. As well systems without bash won't fail. "${BASH_SOURCE[0]}" cannot be used then but "readlink -f" is another reliable method to get a full file path, using another coreutils binary like "dirname". + Execute Jackett with "--NoRestart" option. This has currently not effect, but it assures that the updater never attempts to restart the Jackett process, which is done by the systemd unit already. This avoids possible restart collisions if anything about the updater behaviour changes, e.g. to fix the originating issue. + Remove the "Jackett update complete" print. This is simply wrong if Jackett was stopped ordinarily and the updater itself logs to the same destination, including a "finished to copy files" after completed. Signed-off-by: MichaIng <micha@dietpi.com>
2019-11-05 17:45:28 +00:00
#!/bin/sh
updater: improvements in systemd jackett_launcher (#6270)
2019-10-30 01:58:11 +00:00
# Helper script to fix
# https://github.com/Jackett/Jackett/issues/5208#issuecomment-547565515
jackett_launcher.sh fine tuning (#6297) + Execute script with system default bourne shell. On Debian this is "dash" by default, which has a much lower memory foot print compared to bash. As well systems without bash won't fail. "${BASH_SOURCE[0]}" cannot be used then but "readlink -f" is another reliable method to get a full file path, using another coreutils binary like "dirname". + Execute Jackett with "--NoRestart" option. This has currently not effect, but it assures that the updater never attempts to restart the Jackett process, which is done by the systemd unit already. This avoids possible restart collisions if anything about the updater behaviour changes, e.g. to fix the originating issue. + Remove the "Jackett update complete" print. This is simply wrong if Jackett was stopped ordinarily and the updater itself logs to the same destination, including a "finished to copy files" after completed. Signed-off-by: MichaIng <micha@dietpi.com>
2019-11-05 17:45:28 +00:00
# Get full Jackett root path
JACKETT_DIR="$(dirname "$(readlink -f "$0")")"
updater: improvements in systemd jackett_launcher (#6270)
2019-10-30 01:58:11 +00:00
# Launch Jackett
jackett_launcher.sh fine tuning (#6297) + Execute script with system default bourne shell. On Debian this is "dash" by default, which has a much lower memory foot print compared to bash. As well systems without bash won't fail. "${BASH_SOURCE[0]}" cannot be used then but "readlink -f" is another reliable method to get a full file path, using another coreutils binary like "dirname". + Execute Jackett with "--NoRestart" option. This has currently not effect, but it assures that the updater never attempts to restart the Jackett process, which is done by the systemd unit already. This avoids possible restart collisions if anything about the updater behaviour changes, e.g. to fix the originating issue. + Remove the "Jackett update complete" print. This is simply wrong if Jackett was stopped ordinarily and the updater itself logs to the same destination, including a "finished to copy files" after completed. Signed-off-by: MichaIng <micha@dietpi.com>
2019-11-05 17:45:28 +00:00
${JACKETT_DIR}/jackett --NoRestart
updater: improvements in systemd jackett_launcher (#6270)
2019-10-30 01:58:11 +00:00
# Get user running the service
JACKETT_USER=$(whoami)
# Wait until the updater ends
jackett_launcher.sh fine tuning (#6297) + Execute script with system default bourne shell. On Debian this is "dash" by default, which has a much lower memory foot print compared to bash. As well systems without bash won't fail. "${BASH_SOURCE[0]}" cannot be used then but "readlink -f" is another reliable method to get a full file path, using another coreutils binary like "dirname". + Execute Jackett with "--NoRestart" option. This has currently not effect, but it assures that the updater never attempts to restart the Jackett process, which is done by the systemd unit already. This avoids possible restart collisions if anything about the updater behaviour changes, e.g. to fix the originating issue. + Remove the "Jackett update complete" print. This is simply wrong if Jackett was stopped ordinarily and the updater itself logs to the same destination, including a "finished to copy files" after completed. Signed-off-by: MichaIng <micha@dietpi.com>
2019-11-05 17:45:28 +00:00
while pgrep -u ${JACKETT_USER} JackettUpdater > /dev/null; do
updater: improvements in systemd jackett_launcher (#6270)
2019-10-30 01:58:11 +00:00
sleep 1
done