Open z505 opened 7 years ago
Might also only get it working without tprocess on unix, maybe using assignstream in unix unit, or some other function. Again maybe just using TProcess is best if can't get it working using simple functions, as theoretically TProcess works on all OS's
Webcmd currently just tells the exit code and does not pipe stderr back to the web browser. This may be a limitation of using fpSystem (unix) or it may be possible.
Indeed TProcess would allow more fine control of stderr/stdout. If possible get it working using current way, as tprocess is a bit more complex. But if that is not possible then maybe use TProcess. Might have to fork webcmd to keep the old code in tact for archive purposes as the current system is very simple and just works.
An example of the issue: if a command fails, there is just an exit code which isn't always very helpful. Would be nice to see actual output in text of the command problem (usually stderr has this info).