GitLab

with the introduction of socket creation this log message hasn't been
making sense.  It would be rather confusing and harmful.

dict.values() is an iterable, so we can use it directly in the for statement.
(and we don't modify components within the loop).

this should fix the main problem of this ticket.

this should fix the main problem of this ticket.

This information is used for other module e.g. stats to count running instances
of same module. The address information is seen in the third index of the
array.

 the bind10 daemon

'setstats' is a command duplicate for sending statistics and it was useless
since boss already has same command 'getstats'. Besides, 'getstats' command get
changed. It chacks validity of statistics data before returing. The second
parameter of the 'getstats' is more simpler. The keys of 'owner' and 'data'
needs to be specified.  Statistics data are directly specifed. If such
obsoleted name is specified, the stats module might discard sent data.

This one is mostly the hot-spot cache. The new data source model does
not use it at all. Also, the parameters to tune it were removed.

 * Also set this env variable in isc::log::initLogger()

- if self.clear_config is None was wrong, should just be if self.clear_config
- 'back up' should have been 'create backup of'
- default value for unused parameter rename_config_file in b10-cfgmgr_test.py.in MyConfigManager should have been False, not None
- reordered message file

also extend log message a bit

Use prefix "sockcreator-" for the private temporary directory
used for b10-sockcreator communication.

Discussed in jabber.

Will document separately (was not documented yet).

May break something. It is needed to go through applications and check
their shutdown handlers.

When closing a ModuleCCSession, a 'i am stopping' message is now sent to the ConfigManager, which in turn informs Cmdctl (which then causes bindctl to update its list).

This causes stopped modules to disappear from bindctl until such time that they are enabled or started again, so that config updates and most importantly, commands, do not cause weird timeouts (bindctl will immediately inform you of modules not running)

If it is run from the source code, all programs should be run from
there.

The socket and an address. We don't care about the address, but we still
need to unpack the socket out.