Repository navigation
Cross-seed: external program is logged as launched, but does not execute as expected #1075
Replies: 1 comment
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
When Cross-Seed injects a torrent, it should run an external program configured in the Cross-Seed rules. The external program is a curl call to the Pushover API. qui records “External program launched” in the debug log for both the automatic Cross-Seed trigger and a manual run from the UI, but only the manual run produces a delivered Pushover message.
Steps to reproduce
Create an External Program via Settings → External Programs:
/usr/bin/curlEnsure
/usr/bin/curlis allowed as an External Program inconfig.toml.In Cross-Seed Rules, set Run external program after injection to the External Program created in step 1.
Wait for a cross-seed hit (i.e., Cross-Seed injects a matching torrent into qBittorrent).
Observe the results:
Environment
Relevant logs
Checklist
All reactions