[Top][All Lists]

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

Re: Defualt socket server overriding

From: Wei Shen
Subject: Re: Defualt socket server overriding
Date: Wed, 20 Jun 2007 15:46:45 +0800


On 6/20/07, Thomas Bushnell BSG <tb@becket.net> wrote:
> On 6/20/07, Neal H. Walfield neal@walfield.org> wrote:    
> 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.
SERVERS_SOCKET_PFINET is the name of an env variable. We use the domain augument to determine which env variable to check. For example, if the socket domain is PF_INET, we just check for the SERVERS_SOCKET_PFINET.

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?
This is a completely different case for it is a general mechnism other than specific to socket servers. I have once thoght some other general approches, but feel difficult to judge their rationality myself for lacking knowledge about the Hurd philosophy.
As for the chroot approach, I think we may not expect a new name space but a more flexible way to overriding individule servers in many cases.
Wei Shen

reply via email to

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