--with-zthread-prefix=PFX Prefix where ZTHREAD is installed (optional)
--with-zthread-exec-prefix=PFX Exec prefix where ZTHREAD is installed (optional)
Update, I did the install/configure of ZThreads, but I did not install libtools (do not have root at the moment, am able to get it if I need to though). It gave the same error.
Moofie wrote:Update, I did the install/configure of ZThreads, but I did not install libtools (do not have root at the moment, am able to get it if I need to though). It gave the same error.
Reinstall Z-Threads with --prefix=/usr/ (like AI-Team suggested) and it would work I think.
Moofie wrote:Update, I did the install/configure of ZThreads, but I did not install libtools (do not have root at the moment, am able to get it if I need to though). It gave the same error.
I don't think you need libtools (atleast I don't remember I ever did )
After installing Z-Thread with
Ah, with 0install, you shouldn't call the implementations directly. Always use 0launch or 0alias, only then will it auto-resolve its dependencies.
Edit, as for the script: try the console/config command SPAWN_SCRIPT. It starts scripts the way you want: with stdin coming from ladderlog and the output fed into arma's input. For you:
SPAWN_SCRIPT deathpulse.php
and deathpulse.php needs to be moved from the var/ subfolder to the scripts/ subfolder of your user data directory.
Also, in your launch code, you may have a look at your userconfigdir; it's a config file, not a directory. You should probably just drop both the --userconfigdir and --vardir arguments, the vardir you set is the default anyway.
Nothing launches, but it tries. It has 2 // ^, I that may be the problem but I didn't set any. I putting the full path in the command as well and it gave this
[0] ERROR: User given path "scripts//home/mark/.armagetronad-styct-dedicated/scripts/deathpulse.php" contains a hidden component.
[0] External command '/home/mark/.armagetronad-styct-dedicated/scripts/deathpulse.php' not found anywhere in <datapath>/scripts/
That would be the correct way, the double / doesn't matter. Absolute paths are forbidden for security reasons, all commands can also be triggered by remote admins and you don't want anyone to be able to just run arbitrary scripts on your server.
Maybe the issue is with the php script itself, can you post it? Also, is it possible to launch the script from the shell by entering /home/mark//.armagetronad-styct-dedicated/scripts/deathpulse.php? I dimly remember that not being possible for php, you'll need to write a regular shell script wrapper then.
[0] Remote admin command by Moofie@forums: spawn_script deathpulse.php
[0] Launching scripts from RINCLUDE or maps is not possible for security reasons. Work around it by delegating the actual script launch to a local configuration file.
[0] Remote admin command by Moofie@forums: spawn_script deathpulse.php
[0] Launching scripts from RINCLUDE or maps is not possible for security reasons. Work around it by delegating the actual script launch to a local configuration file.
That just means what it says: No remote triggered start of scripts. We always want two layers of security between us and remote exploit hacks because every layer alone can have flaws. Here, while we do check that the command that is launched really is just the script and not the script plus some payload, those checks may be faulty or get broken by future OSes or be already broken on Unix variants we don't usually test. Or consider the fact that you can pass parameters to scripts: scripts run with full rights of the server, what if a script has a vulnerability parsing its arguments?
Oh, one thing to note: if you start your scripts that way, they need to terminate when they receive EOF or errors on input. The little test script doesn't do that and doesn't terminate and, worse, eats up as much CPU time as it can get.