Challenge: who can background this shell command?

Matthias Rebbe matthias_livecode_150811 at m-r-d.de
Thu Aug 1 09:54:46 EDT 2019


put "/users/matthias/downloads/temp/MailHog > /users/matthias/downloads/temp/hubbabubba.txt 2>&1 &" into tShell

-- above redirects into file and then don´t ask me.. ;)
put shell(tShell)
answer URL "file:/users/matthias/downloads/temp/hubbabubba.txt"
-- answer dialog shows content of file, which contains in my case the address and port it was binded to.


2019/08/01 15:46:01 Using in-memory storage
2019/08/01 15:46:01 [SMTP] Binding to address: 0.0.0.0:1025
[HTTP] Binding to address: 0.0.0.0:8025
2019/08/01 15:46:01 Serving under http://0.0.0.0:8025/ <http://0.0.0.0:8025/>
Creating API v1 with WebPath: 
Creating API v2 with WebPath: 
[APIv2] GET /api/v2/messages
[APIv2] GET /api/v2/jim
[APIv2] GET /api/v2/websocket
[APIv1] KEEPALIVE /api/v1/events


Be aware, that the background process runs untill you kill it from the shell.

Regards,

Matthias


Matthias Rebbe

free tools for Livecoders:
InstaMaker <https://instamaker.dermattes.de/>
WinSignMaker Mac <https://winsignhelper.dermattes.de/>

> Am 01.08.2019 um 15:20 schrieb David Bovill via use-livecode <use-livecode at lists.runrev.com <mailto:use-livecode at lists.runrev.com>>:
> 
> That works in the message box - thanks Matthias.
> 
> The only thing is I can't (yet) tell what port the server is running on - I
> can see from the terminal (using pgrep) the process id of the started
> server - but it does not appear to be serving correctly on the default
> server port...
> 
> Do you think there is a way to redirect the output to Livecode's result or
> it variable - I seem to remember that there have been some changes to that
> to make such a construction possible in Livecode - alternatively maybe the
> output can be directed to a temporary file instead of " /dev/null"???
> 
> Nearly there :)
> 



Matthias Rebbe

free tools for Livecoders:
InstaMaker <https://instamaker.dermattes.de/>
WinSignMaker Mac <https://winsignhelper.dermattes.de/>



More information about the Use-livecode mailing list