Hi,
trying to pick your brains here.
I hope to be able to explain decently what I'm trying to achieve.
This is about the test suite of Net::Statsd::Server, a perl port
of the javascript statsd daemon, and in particular the
t/integration-tests/*.t cases.
Integration here means that the *.t files,
On Thu, Apr 23, 2015 at 05:59:34PM +0200, Cosimo Streppone wrote:
>
> Now, problem.
>
> I'd like to use port 0 to bring up the daemon, so that the test suite
> can be run in parallel without port clashes. With port == 0 the TCP/UDP
> bind will happen on a random free port.
>
> When the fork + ex
On 23. april 2015 19:02, Tim Bunce wrote:
> On Thu, Apr 23, 2015 at 05:59:34PM +0200, Cosimo Streppone wrote:
>>
>> When the fork + exec'd daemon chooses a random port, I need to be able
>> to know which port it has bound itself to, and here lies the problem.
>
> Perhaps dodge the problem by not p
Can you start the server and get the port in the parent process, then fork
and run the tests from the child?
On Thu, Apr 23, 2015 at 11:21 AM, Cosimo Streppone wrote:
> On 23. april 2015 19:02, Tim Bunce wrote:
>
> > On Thu, Apr 23, 2015 at 05:59:34PM +0200, Cosimo Streppone wrote:
> >>
> >> Whe
oops ignore my last message, obviously forking the server is a dumb idea.
On Thu, Apr 23, 2015 at 11:23 AM, Chad Granum wrote:
> Can you start the server and get the port in the parent process, then fork
> and run the tests from the child?
>
> On Thu, Apr 23, 2015 at 11:21 AM, Cosimo Streppone
On 23. april 2015 20:23, Chad Granum wrote:
> Can you start the server and get the port in the parent process, then
> fork and run the tests from the child?
Unfortunately that is not possible, as client and server code
are completely separated, and I'd like to run
the test suite against the javas
On Thu, Apr 23, 2015 at 08:21:28PM +0200, Cosimo Streppone wrote:
> On 23. april 2015 19:02, Tim Bunce wrote:
>
> > On Thu, Apr 23, 2015 at 05:59:34PM +0200, Cosimo Streppone wrote:
> >>
> >> When the fork + exec'd daemon chooses a random port, I need to be able
> >> to know which port it has boun
Il 23/04/2015 21:53, Tim Bunce ha scritto:
How is "the port number is saved into the file" when you don't know
which port it has bound itself to?
The daemon starts and binds using port 0. Still within the daemon code,
I can then query for the used port, through regular socket calls.
After that
