[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Defualt socket server overriding

From: Thomas Bushnell BSG
Subject: Re: Defualt socket server overriding
Date: Tue, 19 Jun 2007 20:26:05 -0700

On Wed, 2007-06-20 at 11:11 +0800, Wei Shen wrote:
> Hi,
> On 6/20/07, Neal H. Walfield <neal@walfield.org> wrote: 
>         > (1) Add a set of new environment variables, e.g.
>         PFINETSERVER for the pf_inet server and PFLOCALSERVER for the
>         pf_local server. 
>         We should have consistent naming between node names and
>         environment variables.  The default node names
>         are /servers/socket/{2,pfinet}, etc.  Perhaps have
>         SERVERS_SOCKET_PFINET be the name of the environment variable
>         to use.

I wonder how you plan to implement this.  The library does not use 
the #define symbol in practice; it uses /servers/socket/%d and fills in
%d from the first argument to the socket() call.

It seems to me that an implementation which makes assumptions about how
people construct names in /servers is unreliable.

What about a different strategy, one more "hurdish"?  For example, run
the program in a pseudo-chroot which overrides the behavior of nodes
inside /servers?


Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]