[CSI] Community Software Installer 2.6.1 (OLD THREAD)

[joshua.lyon]

(10-12-2009 08:56 PM)joshua.lyon Wrote:  It works fine on my PCH as well, but some users report having issues with the cron job at some point. It looks like the only thing that is consistent between the two users is that the issue occurs when they reboot the PCH.

I'll test out rebooting my PCH tonight to see how it affects my cron job.

I tried a reboot and it does in fact remove the cron entry. Is this also a known issue/design? I thought CSI (appinit) would automatically redo the cron entry upon reboot?

--
Also - just as a heads up, I tried running the appinit.cgi command from a PHP application and while appears to successfully run, some of the core functionality doesn't appear to work -- such as the updating / adding of cron entries.

Example:

PHP Code:

unset($output); // clear the array in case we've already used it
$status = NULL; // clear the status in case we've used it
exec("/share/Apps/AppInit/appinit.cgi rescan NewzBook", $output, $status); // run the command and get the screen output and status
echo "The command returned a status of $status <br/>"; // this outputs 0 (it successfully ran)
echo "<pre>".implode("<br/>", $output)."</pre>"; // this shows the output below 


The output from the appinit rescan command from PHP is:

Code:

Found hardware type: Syabas A/B type


Application Initializer version 1.12
---------------------------------------
Checking for new version: up to date
Checking Application Initializer profile: Valid
Rescanning NewzBook: Done

The thing is, if I do a crontab -l just after a reboot, then run the debug page which includes the appinit rescan command, then run the crontab -l command again the cron entry never gets added. (fyi crontab results in a exit code of 127 from php -- which typically indicates the command cannot be found)

However, if I run the appinit rescan command from the shell (telnet), it does update the cron entry.