8 Commits (6b35840ba2bcb356df6d2a23f994a7cdf8984ab6)

Author	SHA1	Message	Date
Guillem Jover	50ecc15441	TT#37401 Use Unix sockets to avoid relying on hostnames for localhost/loopback ... If the file /etc/hosts gets handled by templates, as ongoing changes attempt to do, there's a problem because /etc/hosts gets truncated to create a new file when it's needed to generate itself, to resolve the "localhost" string as hostname, so the generation fails and /etc/hosts gets empty at that point, affecting the system until restored. The simplest way to break that cycle is to switch to Unix sockets. Change-Id: I1e33ead6a134625346b9cf1beb09a7bdbfdfc8d2	8 years ago
Michael Prokop	e40ec0137e	MT#16391 Fix regression regarding unset NGCP_PORTFILE ... Fix regression from d62433cf93 if NGCP_PORTFILE is unset Change-Id: I9ac5e793d1a3bc4d8e3094c6b70987fcf42cf978	9 years ago
Michael Prokop	d62433cf93	MT#16391 Don't hardcode tt2-daemon's port file ... For testing without root permissions we need a different path than /var/run/ngcpcfg.port. Change-Id: I268d5c61a8caa0f7fe737813c02cafa92db79a35	9 years ago
Alexander Lutay	e35944e2b5	MT#12547 Remove hardcoded port 42042 from tt2-wrapper/tt2-daemon ... We will use first free port instead which will be stored into /var/run/ngcpcfg.port file while tt2-daemon is up and running. Change-Id: I1a918f865d87863eef7d34be8abd1032282220b8	11 years ago
Alexander Lutay	e3eda0cb3b	MT#5027 Speed up 'build' runs by using Perl daemon	13 years ago
Alexander Lutay	9206aa868a	Revert "MT#4141 Speed up 'build' runs by loading YAML files only once" ... This reverts commit 335d53c95c.	13 years ago
Michael Prokop	335d53c95c	MT#4141 Speed up 'build' runs by loading YAML files only once ... When runnning 'ngcpcfg build' (which is also executed when running 'ngcpcfg apply') we waste quite some time with loading the same YAML configuration files and merging them again and again. In a 'ngcpcfg build' run we don't have to re-load and merge those configuration files again and again (since they won't modify during a single run), instead just load+merge them *once* and re-use the result on all the following execution steps in the same run. Original: | # time ngcpcfg apply >/dev/null | ngcpcfg apply > /dev/null 149.01s user 9.49s system 96% cpu 2:43.57 total Reworked optimized runs: | # time ngcpcfg apply >/dev/null | ngcpcfg apply > /dev/null 81.25s user 8.62s system 95% cpu 1:34.17 total For debugging purposes you can execute 'ngcpcfg build' under NO_REUSE=1 to not use this feature, executing it under 'DEBUG=1' won't remove the so called reuse file which stores the merged configuration data. Thanks: Alexander Lutay for the initial patch and idea	13 years ago
Michael Prokop	3436c08361	Initial checkin	13 years ago