Help talk:Toolforge/Web/Archives/2014
Appearance
Latest comment: 10 years ago by Tim Landscheidt in topic portgrabber
![]() |
Please do not post any new comments on this page. This is a discussion archive See current discussion or the archives index. |
portgrabber
I'm not seeing portgrabber(1) anywhere. Where is it, or what are the up-to-date instructions for running a non-PHP Web service? abartov (talk) 07:36, 14 December 2014 (UTC)
- There is no documentation for this. The source can be found here, i. e. basically connect to
/tmp/sock.portgranter
, send$tool\n
there, receive a port number back, connect to port 8282 on tools-webproxy, send.*\n$host:$port\n
there, leave the sockets open until your server terminates. Note that for non-PHP = Tomcat, there iswebservice tomcat start
. --Tim Landscheidt (talk) 07:53, 14 December 2014 (UTC)- Thanks, Tim! This was helpful. I now see portgrabber is reachable on the grid, even if not from the tool's command line. I ran into more difficulty running my server, but it does not appear to be related to portgrabber, but to the environment. abartov (talk) 21:27, 14 December 2014 (UTC)
- I'm sorry, I misread your question to mean "how does portgrabber work", not "how does one use portgrabber". It's rather pretty easy: Call it with
portgrabber $tool $command [$arg1…$argn]
, and it will grab a port number and call$command [$arg1…$argn] $port
(leaving the sockets open until$command
terminates). --Tim Landscheidt (talk) 21:44, 14 December 2014 (UTC)
- I'm sorry, I misread your question to mean "how does portgrabber work", not "how does one use portgrabber". It's rather pretty easy: Call it with
- Thanks, Tim! This was helpful. I now see portgrabber is reachable on the grid, even if not from the tool's command line. I ran into more difficulty running my server, but it does not appear to be related to portgrabber, but to the environment. abartov (talk) 21:27, 14 December 2014 (UTC)