[Nix-dev] Multiple instances - detecting resource collisions - nixos module system question
moritz at tarn-vedra.de
Sun Jan 18 12:51:58 CET 2015
Luca Bruno <lethalman88 at gmail.com> writes:
> On 15/01/2015 01:23, Nicolas Pierron wrote:
>> On Wed, Jan 14, 2015 at 11:17 PM, Marc Weber <marco-oweber at gmx.de> wrote:
>>> If you use multiple apaches/nginx/mysql/postgresql/whatever instances
>>> its likely to miss adjusting the port or whatsoever. Therefore I'd like
>>> to implement a simple "resource tracking" module which fails if a
>>> resource such as tcp/ip port or socket or such gets used multiple times.
>> This is awesome!
> This is a mess:
> 1) A service can bind to multiple ip and ports.
So we can just use a list of ports instead of a single one.
> 2) There's not only tcp.
So two lists? UDP and TCP ports.
> 3) A service could start listening dynamically on other ports at
This is a valid point. An approach like this needs to trust the services
not to lie about their list of used ports.
> This is enough for saying it's going to be too complicated to check for
> conflicts with little gain and many false positives.
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 818 bytes
Desc: not available
Url : http://lists.science.uu.nl/pipermail/nix-dev/attachments/20150118/9988412e/attachment.bin
More information about the nix-dev