Hi Nixers, Say you have a service and you make a change to the service code. Nix will restart the service.
Now say my service code is smart enough to do hot swapping of components al a Erlang style. Is it possible to tell nix not to restart the service but instead give the running executable a long string and let the executable be responsible for making changes to it's environment in a declarative manner? kr/sjm _______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
