On 05/28/2013 12:44 PM, Martin Lülf wrote:
Hi,

I would solve this with a small PHP Script on the webserver (or whatever scripting language is available on the webserver). The script can evaluate the called URL including parameters.

So in the build gnuradio script you would call something like this
wget http://example.com/script.php?param1=5&param2=pi


The Script on the webserver will now have access to param1 and param2 and can store them in a Database, or whatever you would like to do and can return (echo) a few charakters (e.g. 1 ok, 0 malformed parameter).
Yes, I was thinking something through wget as well...


This way the build gnuradio script can then evaluate the content of the downloaded file to see if anything went wrong.

For this to work you only need HTTP access to the script webserver on the install PC. Many PCs are behind Firewalls that drop traffic on Port 25 if you try to use Email, but port 80 is almost always oppen.

I also agree with Jonathan, that sending back feedback should be a opt-in decision during the installation.

Yours
Martin

I'll have to think about this. I don't want to add even more work to my workload, but I would like to understand what fraction of build-gnuradio
  invocations are failing, and why.




--
Marcus Leech
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org


_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to