Peter Rajnoha 847e2856a2 config: require dm_config_create_value for dm_config_node's value ... If we were defining a section (which is a node without a value) and the value was created automatically on dm_config_create_node call, we were wasting resources as the next step after creating the config node itself was assigning NULL for the node's value. The dm_config_node_create + dm_config_create_value sequence should be used instead for settings and dm_config_node_create alone for sections. The majority of the code already used the correct sequence. Though with dm_config_node_create fn creating the value as well, the pool memory was being trashed this way. This patch removes the node value initialization on dm_config_create_node fn call and keeps it for the direct dm_config_create_value fn call.		2012-08-27 14:33:54 +02:00
..
clvmd	clvmd,lvmetad: check for fcntl result	2012-08-23 14:38:48 +02:00
cmirrord	cmirrord: check for result of chdir	2012-08-23 14:37:20 +02:00
dmeventd	cleanup: add error message and simplify creation	2012-08-23 14:37:38 +02:00
lvmetad	config: require dm_config_create_value for dm_config_node's value	2012-08-27 14:33:54 +02:00
Makefile.in	Reflect new file locations, include file updates etc.	2012-02-28 18:35:04 +00:00