Re: [Monotone-devel] automate serve?

[Stephen Leake]

Thomas Keller <address@hidden> writes:

> Am 26.09.10 16:36, schrieb Stephen Leake:
>> In implementing the DVC front-end for automate sync, I've run into a
>> problem.
>> 
>> If I use ssh: or file: netsync schemes, the mtn process that is started
>> outputs startup error messages that are not properly packetized for
>> automate stdio. [...]
>
> If you read over this again, how do you think would an automate version
> of serve make any changes to this behaviour? The mtn instance that is
> called would still use a completely different package stream (which must
> not be intermixed with the packet stream of the parent process) 

Ah, right. 

I could start the remote process with 'echo "l5:servee" | mtn automate
stdio".

The remote mtn would output packets, but the command counts would be
mixed up.

And the automate stdio header info would not be expected by the netsync
protocol. That could be handled by 'automate sync'; it could check that
the remote stdio is properly started before calling netsync.

Ah; all I really need is for netsync.cc call_server to incorporate the
remote error message in the local error message when the session fails
to start properly.

I don't see how to add that at the moment, but it should be doable.
Something like 'sess->get_remote_error()'.

For now, I'll live with the current error I get; my front-end reports
"unexpected output from mtn", and the actual error is clear.

-- 
-- Stephe