[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 11:11:45 +0800


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 agree that  SERVERS_SOCKET_PFINET seems better. I proposed PFINETSERVER just for the compliance with env variables already in use: CRASHSERVER for the crash server and EXECSERVERS for exec.
A nice feature would be the option to use a file descriptor rather
than a symbolic name.  This could take the form fd:X where X is some
number.  This allows for selected access delegation (consider:
SERVERS_SOCKET_PFINET=fd:3 prog 3</path/to/my/pfinet) and removes a
naming issue.  See section 3.4 of the critique [1] for an example of
the problems that can arise through the use of symbolic names.
Good idea. I have considered file descriptor and will think over it.
"SERVERS_SOCKET_PFINET=fd:3 prog 3</path/to/my/pfinet" - what does "prog 3<" mean, three overriding names behind?

reply via email to

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