Hi,
On Mon, Jun 30, 2008 at 03:10:13PM +0200, zhengda wrote:
> [EMAIL PROTECTED] wrote:
>> AIUI every process has it's own port for proc, right?
>>
>> So I think all you need to do is for every client that contacts the
>> proc proxy, to create a distinct port to the real proc server, and
>> forwa
[EMAIL PROTECTED] wrote:
The only difference between translators and other programs is that a
translator uses the bootstrap port, while other programs ignore it. As
the translator subprocess is forked from the "outer" helper program
invoked through settrans, the bootstrap port is copied to it. Th
Hi,
On Thu, Jun 26, 2008 at 07:46:55PM +0200, zhengda wrote:
> [EMAIL PROTECTED] wrote:
>> These should be fixable by reversing the command I think:
>>
>> settrans -afgpc /root/socket2/2 proc_proxy /root/hurd/pfinet/pfinet
>> -i eth0 -a 192.168.2.11 -g 192.168.2.1 -m 255.255.255.0
>>
> In this
[EMAIL PROTECTED] wrote:
3. If the translator is set in the passive mode, it is started by the
file system server. It seems that I don't have a chance to override
its proc server.
These should be fixable by reversing the command I think:
settrans -afgpc /root/socket2/2 proc_proxy /root/h
Hi,
On Tue, Jun 24, 2008 at 10:56:03PM +0200, zhengda wrote:
> I want to write a proxy of the proc server (proc_proxy), so I can
> provide a pseudo master device port to the translator without changing
> its code.
>
> My first idea was to create a message server which handles all RPCs in
> proces
Hi everyone,
I want to write a proxy of the proc server (proc_proxy), so I can
provide a pseudo master device port to the translator without changing
its code.
My first idea was to create a message server which handles all RPCs in
process.defs. When a request comes, the message server calls
