shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00
Code Releases Activity
455f23586f
lvm2/lib/config/config.h

241 lines
11 KiB
C
Raw Normal View History

o Populating with stuff from experimental
2001-08-21 16:56:08 +04:00
/*
Update copyright notices.
2004-03-30 23:35:44 +04:00
* Copyright (C) 2001-2004 Sistina Software, Inc. All rights reserved.
Fix inconsistent licence notices: executables are GPLv2; libraries LGPLv2.1.
2007-08-21 00:55:30 +04:00
* Copyright (C) 2004-2007 Red Hat, Inc. All rights reserved.
o Populating with stuff from experimental
2001-08-21 16:56:08 +04:00
*
Update copyright notices.
2004-03-30 23:35:44 +04:00
* This file is part of LVM2.
*
* This copyrighted material is made available to anyone wishing to use,
* modify, copy, or redistribute it subject to the terms and conditions
Fix inconsistent licence notices: executables are GPLv2; libraries LGPLv2.1.
2007-08-21 00:55:30 +04:00
* of the GNU Lesser General Public License v.2.1.
Update copyright notices.
2004-03-30 23:35:44 +04:00
*
Fix inconsistent licence notices: executables are GPLv2; libraries LGPLv2.1.
2007-08-21 00:55:30 +04:00
* You should have received a copy of the GNU Lesser General Public License
Update copyright notices.
2004-03-30 23:35:44 +04:00
* along with this program; if not, write to the Free Software Foundation,
* Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
o Populating with stuff from experimental
2001-08-21 16:56:08 +04:00
*/
lvactivate checkpoint commit
2001-09-25 16:49:28 +04:00
#ifndef _LVM_CONFIG_H
#define _LVM_CONFIG_H
Use hash, bitset, malloc, pool from libdevmapper.
2005-10-17 03:03:59 +04:00
#include "lvm-types.h"
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
#include "defaults.h"
Use hash, bitset, malloc, pool from libdevmapper.
2005-10-17 03:03:59 +04:00
config: add vsn macro The 'vsn' macro encodes the LVM2 version major, minor and patchlevel number in a packed form using 16 bits.
2013-03-05 19:39:36 +04:00
/* 16 bits: 3 bits for major, 4 bits for minor, 9 bits for patchlevel */
cleanup: comments and a message
2013-07-25 01:10:37 +04:00
/* FIXME Max LVM version supported: 7.15.511. Extend bits when needed. */
config: add vsn macro The 'vsn' macro encodes the LVM2 version major, minor and patchlevel number in a packed form using 16 bits.
2013-03-05 19:39:36 +04:00
#define vsn(major, minor, patchlevel) (major << 13 | minor << 9 | patchlevel)
Support tagged config files.
2004-05-04 22:28:15 +04:00
struct device;
struct cmd_context;
Another sync point - numerous fixes & clean ups.
2003-07-05 02:34:56 +04:00
config: add config_source_t type to identify configuration source A helper type that helps with identification of the configuration source which makes handling the configuration cascade a bit easier, mainly removing and adding configuration trees to cascade dynamically. Currently, the possible types are: CONFIG_UNDEFINED - configuration is not defined yet (not initialized) CONFIG_FILE - one file configuration CONFIG_MERGED_FILES - configuration that is a result of merging more files into one CONFIG_STRING - configuration string typed on cmd line directly CONFIG_PROFILE - profile configuration (the new type of configuration, patches will follow...) Also, generalize existing "remove_overridden_config_tree" to work with configuration type identification in a cascade. Before, it was just the CONFIG_STRING we used. Now, we need some more to add in a cascade (like the CONFIG_PROFILE). So, we have: struct dm_config_tree *remove_config_tree_by_source(struct cmd_context *cmd, config_source_t source); config_source_t config_get_source_type(struct dm_config_tree *cft); ... for removing the tree by its source type from the cascade and simply getting the source type.
2013-06-25 14:25:43 +04:00
typedef enum {
CONFIG_UNDEFINED, /* undefined/uninitialized config */
CONFIG_FILE, /* one file config */
CONFIG_MERGED_FILES, /* config that is a result of merging more config files */
CONFIG_STRING, /* config string typed on cmdline using '--config' arg */
CONFIG_PROFILE /* profile config */
} config_source_t;
config: add support for loading profiles This patch adds --profile arg to lvm cmds and adds config/profile_dir configuration setting to select the directory where profiles are stored By default it's /etc/lvm/profile. The profiles are added by using new "add_profile" fn and then loaded using the "load_profile" fn. All profiles are stored in a cmd context within the new "struct profile_params": struct profile_params { const char *dir; struct profile *global_profile; struct dm_list profiles_to_load; struct dm_list profiles; }; ...where "dir" is the directory with profiles, "global_profile" is the profile that is set globally via the --profile arg (IOW, not set per VG/LV basis based on metadata record) and the "profiles" is the list with loaded profiles.
2013-06-25 14:27:04 +04:00
struct profile {
struct dm_list list;
const char *name;
struct dm_config_tree *cft;
};
struct profile_params {
const char *dir; /* subdir in LVM_SYSTEM_DIR where LVM looks for profiles */
struct profile *global_profile; /* profile that overrides any other VG/LV-based profile ('--profile' cmd line arg) */
struct dm_list profiles_to_load;/* list of profiles which are only added, but still need to be loaded for any use */
struct dm_list profiles; /* list of profiles which are loaded already and which are ready for use */
};
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
#define CFG_PATH_MAX_LEN 64
/*
* Structures used for definition of a configuration tree.
*/
/* configuration definition item type (for item's accepted types) */
typedef enum {
config: fix bitfield for section Since the cfg_def_type_t is used as bitfield in some tests, use bitshifting to create valid bit sequence. (in release fix)
2013-04-29 14:38:56 +04:00
CFG_TYPE_SECTION = 1 << 0, /* section */
CFG_TYPE_ARRAY = 1 << 1, /* setting */
CFG_TYPE_BOOL = 1 << 2, /* setting */
CFG_TYPE_INT = 1 << 3, /* setting */
CFG_TYPE_FLOAT = 1 << 4, /* setting */
CFG_TYPE_STRING = 1 << 5, /* setting */
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
} cfg_def_type_t;
config: add CFG_DEFAULT_RUN_TIME for config options with runtime defaults Previously, we declared a default value as undefined ("NULL") for settings which require runtime context to be set first (e.g. settings for paths that rely on SYSTEM_DIR environment variable or they depend on any other setting in some way). If we want to output default values as they are really used in runtime, we should make it possible to define a default value as function which is evaluated, not just providing a firm constant value as it was before. This patch defines simple prototypes for such functions. Also, there's new helper macros "cfg_runtime" and "cfg_array_runtime" - they provide exactly the same functionality as the original "cfg" and "cfg_array" macros when defining the configuration settings in config_settings.h, but they don't set the constant default value. Instead, they automatically link the configuration setting definition with one of these functions: typedef int (*t_fn_CFG_TYPE_BOOL) (struct cmd_context *cmd, struct profile *profile); typedef int (*t_fn_CFG_TYPE_INT) (struct cmd_context *cmd, struct profile *profile); typedef float (*t_fn_CFG_TYPE_FLOAT) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_STRING) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_ARRAY) (struct cmd_context *cmd, struct profile *profile); (The new macros actually set the CFG_DEFAULT_RUNTIME flag properly and set the default value link to the function accordingly). Then such configuration setting requires a function of selected type to be defined. This function has a predefined name: get_default_<id> ...where the <id> is the id of the setting as defined in config_settings.h. For example "backup_archive_dir_CFG" if defined as a setting with default value evaluated in runtime with "cfg_runtime" will automatically have "get_default_backup_archive_dir_CFG" function linked to this setting to get the default value.
2014-03-03 15:34:11 +04:00
/* function types to evaluate default value at runtime */
typedef int (*t_fn_CFG_TYPE_BOOL) (struct cmd_context *cmd, struct profile *profile);
typedef int (*t_fn_CFG_TYPE_INT) (struct cmd_context *cmd, struct profile *profile);
typedef float (*t_fn_CFG_TYPE_FLOAT) (struct cmd_context *cmd, struct profile *profile);
typedef const char* (*t_fn_CFG_TYPE_STRING) (struct cmd_context *cmd, struct profile *profile);
typedef const char* (*t_fn_CFG_TYPE_ARRAY) (struct cmd_context *cmd, struct profile *profile);
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
/* configuration definition item value (for item's default value) */
typedef union {
config: add CFG_DEFAULT_RUN_TIME for config options with runtime defaults Previously, we declared a default value as undefined ("NULL") for settings which require runtime context to be set first (e.g. settings for paths that rely on SYSTEM_DIR environment variable or they depend on any other setting in some way). If we want to output default values as they are really used in runtime, we should make it possible to define a default value as function which is evaluated, not just providing a firm constant value as it was before. This patch defines simple prototypes for such functions. Also, there's new helper macros "cfg_runtime" and "cfg_array_runtime" - they provide exactly the same functionality as the original "cfg" and "cfg_array" macros when defining the configuration settings in config_settings.h, but they don't set the constant default value. Instead, they automatically link the configuration setting definition with one of these functions: typedef int (*t_fn_CFG_TYPE_BOOL) (struct cmd_context *cmd, struct profile *profile); typedef int (*t_fn_CFG_TYPE_INT) (struct cmd_context *cmd, struct profile *profile); typedef float (*t_fn_CFG_TYPE_FLOAT) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_STRING) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_ARRAY) (struct cmd_context *cmd, struct profile *profile); (The new macros actually set the CFG_DEFAULT_RUNTIME flag properly and set the default value link to the function accordingly). Then such configuration setting requires a function of selected type to be defined. This function has a predefined name: get_default_<id> ...where the <id> is the id of the setting as defined in config_settings.h. For example "backup_archive_dir_CFG" if defined as a setting with default value evaluated in runtime with "cfg_runtime" will automatically have "get_default_backup_archive_dir_CFG" function linked to this setting to get the default value.
2014-03-03 15:34:11 +04:00
/* static value - returns a variable */
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
const int v_CFG_TYPE_BOOL, v_CFG_TYPE_INT;
const float v_CFG_TYPE_FLOAT;
const char *v_CFG_TYPE_STRING, *v_CFG_TYPE_ARRAY;
config: add CFG_DEFAULT_RUN_TIME for config options with runtime defaults Previously, we declared a default value as undefined ("NULL") for settings which require runtime context to be set first (e.g. settings for paths that rely on SYSTEM_DIR environment variable or they depend on any other setting in some way). If we want to output default values as they are really used in runtime, we should make it possible to define a default value as function which is evaluated, not just providing a firm constant value as it was before. This patch defines simple prototypes for such functions. Also, there's new helper macros "cfg_runtime" and "cfg_array_runtime" - they provide exactly the same functionality as the original "cfg" and "cfg_array" macros when defining the configuration settings in config_settings.h, but they don't set the constant default value. Instead, they automatically link the configuration setting definition with one of these functions: typedef int (*t_fn_CFG_TYPE_BOOL) (struct cmd_context *cmd, struct profile *profile); typedef int (*t_fn_CFG_TYPE_INT) (struct cmd_context *cmd, struct profile *profile); typedef float (*t_fn_CFG_TYPE_FLOAT) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_STRING) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_ARRAY) (struct cmd_context *cmd, struct profile *profile); (The new macros actually set the CFG_DEFAULT_RUNTIME flag properly and set the default value link to the function accordingly). Then such configuration setting requires a function of selected type to be defined. This function has a predefined name: get_default_<id> ...where the <id> is the id of the setting as defined in config_settings.h. For example "backup_archive_dir_CFG" if defined as a setting with default value evaluated in runtime with "cfg_runtime" will automatically have "get_default_backup_archive_dir_CFG" function linked to this setting to get the default value.
2014-03-03 15:34:11 +04:00
/* run-time value - evaluates a function */
t_fn_CFG_TYPE_BOOL fn_CFG_TYPE_BOOL;
t_fn_CFG_TYPE_INT fn_CFG_TYPE_INT;
t_fn_CFG_TYPE_FLOAT fn_CFG_TYPE_FLOAT;
t_fn_CFG_TYPE_STRING fn_CFG_TYPE_STRING;
t_fn_CFG_TYPE_ARRAY fn_CFG_TYPE_ARRAY;
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
} cfg_def_value_t;
/* configuration definition item flags: */
/* whether the configuration item name is variable */
#define CFG_NAME_VARIABLE 0x01
/* whether empty value is allowed */
#define CFG_ALLOW_EMPTY 0x02
/* whether the configuration item is for advanced use only */
#define CFG_ADVANCED 0x04
config: add validation for configuration profiles Besides the classical configuration checks (type checking and checking whether the item is recognized by lvm tools) for profiles, do an extra check whether the configuration setting is customizable by a profile at all. Give a warning message if not.
2013-06-26 18:27:28 +04:00
/* whether the configuration item is not officially supported */
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
#define CFG_UNSUPPORTED 0x08
config: add validation for configuration profiles Besides the classical configuration checks (type checking and checking whether the item is recognized by lvm tools) for profiles, do an extra check whether the configuration setting is customizable by a profile at all. Give a warning message if not.
2013-06-26 18:27:28 +04:00
/* whether the configuration item is customizable by a profile */
#define CFG_PROFILABLE 0x10
dumpconfig: comment out config lines without default values defined To make "lvm dumpconfig --type default" output to be usable like any other config, we need to comment out lines that have no default value defined. Otherwise, we'd have the output with config options with blank or zero values which is not the same as when the value is not defined! And such configuration can't be feed into lvm again without further edits. So let's fix this. Currently this covers these configuration options exactly: devices/loopfiles devices/preferred_names devices/filter devices/global_filter devices/types allocation/cling_tag_list global/format_libraries global/segment_libraries activation/volume_list activation/auto_activation_volume_list activation/read_only_volume_list activation/mlock_filter metadata/dirs metadata/disk_areas metadata/disk_areas/<disk_area> metadata/disk_areas/<disk_area>/start_sector metadata/disk_areas/<disk_area>/size metadata/disk_areas/<disk_area>/id tags/<tag> tags/<tag>/host_list
2014-02-25 14:05:23 +04:00
/* whether the default value is undefned */
#define CFG_DEFAULT_UNDEFINED 0x20
config: add CFG_DEFAULT_RUN_TIME for config options with runtime defaults Previously, we declared a default value as undefined ("NULL") for settings which require runtime context to be set first (e.g. settings for paths that rely on SYSTEM_DIR environment variable or they depend on any other setting in some way). If we want to output default values as they are really used in runtime, we should make it possible to define a default value as function which is evaluated, not just providing a firm constant value as it was before. This patch defines simple prototypes for such functions. Also, there's new helper macros "cfg_runtime" and "cfg_array_runtime" - they provide exactly the same functionality as the original "cfg" and "cfg_array" macros when defining the configuration settings in config_settings.h, but they don't set the constant default value. Instead, they automatically link the configuration setting definition with one of these functions: typedef int (*t_fn_CFG_TYPE_BOOL) (struct cmd_context *cmd, struct profile *profile); typedef int (*t_fn_CFG_TYPE_INT) (struct cmd_context *cmd, struct profile *profile); typedef float (*t_fn_CFG_TYPE_FLOAT) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_STRING) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_ARRAY) (struct cmd_context *cmd, struct profile *profile); (The new macros actually set the CFG_DEFAULT_RUNTIME flag properly and set the default value link to the function accordingly). Then such configuration setting requires a function of selected type to be defined. This function has a predefined name: get_default_<id> ...where the <id> is the id of the setting as defined in config_settings.h. For example "backup_archive_dir_CFG" if defined as a setting with default value evaluated in runtime with "cfg_runtime" will automatically have "get_default_backup_archive_dir_CFG" function linked to this setting to get the default value.
2014-03-03 15:34:11 +04:00
/* whether the defualt value is calculated during run time */
#define CFG_DEFAULT_RUN_TIME 0x40
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
/* configuration definition item structure */
typedef struct cfg_def_item {
int id; /* ID of this item */
int parent; /* ID of parent item */
const char *name; /* name of the item in configuration tree */
config: use int for type Since the type is used for 'or' operation of enumerated bit fields, it doesn't not have type cfg_def_type_t - use proper int type for bitmask.
2013-11-25 16:44:46 +04:00
int type; /* configuration item type (bits of cfg_def_type_t) */
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
cfg_def_value_t default_value; /* default value (only for settings) */
uint16_t flags; /* configuration item definition flags */
uint16_t since_version; /* version this item appeared in */
const char *comment; /* brief comment */
} cfg_def_item_t;
config: use config checks and add support for creating trees from config definition (config_def_create_tree fn) Configuration checking is initiated during config load/processing (_process_config fn) which is part of the command context creation/refresh. This patch also defines 5 types of trees that could be created from the configuration definition (config_settings.h), the cfg_def_tree_t: - CFG_DEF_TREE_CURRENT that denotes a tree of all the configuration nodes that are explicitly defined in lvm.conf/--config - CFG_DEF_TREE_MISSING that denotes a tree of all missing configuration nodes for which default valus are used since they're not explicitly used in lvm.conf/--config - CFG_DEF_TREE_DEFAULT that denotes a tree of all possible configuration nodes with default values assigned, no matter what the actual lvm.conf/--config is - CFG_DEF_TREE_NEW that denotes a tree of all new configuration nodes that appeared in given version - CFG_DEF_TREE_COMPLETE that denotes a tree of the whole configuration tree that is used in LVM2 (a combination of CFG_DEF_TREE_CURRENT + CFG_DEF_TREE_MISSING). This is not implemented yet, it will be added later... The function that creates the definition tree of given type: struct dm_config_tree *config_def_create_tree(struct config_def_tree_spec *spec); Where the "spec" specifies the tree type to be created: struct config_def_tree_spec { cfg_def_tree_t type; /* tree type */ uint16_t version; /* tree at this LVM2 version */ int ignoreadvanced; /* do not include advanced configs */ int ignoreunsupported; /* do not include unsupported configs */ }; This tree can be passed to already existing functions that write the tree on output (like we already do with cmd->cft). There is a new lvm.conf section called "config" with two new options: - config/checks which enables/disables checking (enabled by default) - config/abort_on_errors which enables/disables aborts on any type of mismatch found in the config (disabled by default)
2013-03-05 20:36:10 +04:00
/* configuration definition tree types */
typedef enum {
CFG_DEF_TREE_CURRENT, /* tree of nodes with values currently set in the config */
CFG_DEF_TREE_MISSING, /* tree of nodes missing in current config using default values */
CFG_DEF_TREE_COMPLETE, /* CURRENT + MISSING, the tree actually used within execution, not implemented yet */
CFG_DEF_TREE_DEFAULT, /* tree of all possible config nodes with default values */
dumpconfig: add --type profilable The --type profilable shows all config settings that are customizable by profiles: raw/~ $ lvm dumpconfig --type profilable allocation { thin_pool_zero=1 thin_pool_discards="passdown" thin_pool_chunk_size=64 } activation { thin_pool_autoextend_threshold=100 thin_pool_autoextend_percent=20 }
2013-07-09 11:57:46 +04:00
CFG_DEF_TREE_NEW, /* tree of all new nodes that appeared in given version */
CFG_DEF_TREE_PROFILABLE /* tree of all nodes that are customizable by profiles */
config: use config checks and add support for creating trees from config definition (config_def_create_tree fn) Configuration checking is initiated during config load/processing (_process_config fn) which is part of the command context creation/refresh. This patch also defines 5 types of trees that could be created from the configuration definition (config_settings.h), the cfg_def_tree_t: - CFG_DEF_TREE_CURRENT that denotes a tree of all the configuration nodes that are explicitly defined in lvm.conf/--config - CFG_DEF_TREE_MISSING that denotes a tree of all missing configuration nodes for which default valus are used since they're not explicitly used in lvm.conf/--config - CFG_DEF_TREE_DEFAULT that denotes a tree of all possible configuration nodes with default values assigned, no matter what the actual lvm.conf/--config is - CFG_DEF_TREE_NEW that denotes a tree of all new configuration nodes that appeared in given version - CFG_DEF_TREE_COMPLETE that denotes a tree of the whole configuration tree that is used in LVM2 (a combination of CFG_DEF_TREE_CURRENT + CFG_DEF_TREE_MISSING). This is not implemented yet, it will be added later... The function that creates the definition tree of given type: struct dm_config_tree *config_def_create_tree(struct config_def_tree_spec *spec); Where the "spec" specifies the tree type to be created: struct config_def_tree_spec { cfg_def_tree_t type; /* tree type */ uint16_t version; /* tree at this LVM2 version */ int ignoreadvanced; /* do not include advanced configs */ int ignoreunsupported; /* do not include unsupported configs */ }; This tree can be passed to already existing functions that write the tree on output (like we already do with cmd->cft). There is a new lvm.conf section called "config" with two new options: - config/checks which enables/disables checking (enabled by default) - config/abort_on_errors which enables/disables aborts on any type of mismatch found in the config (disabled by default)
2013-03-05 20:36:10 +04:00
} cfg_def_tree_t;
/* configuration definition tree specification */
struct config_def_tree_spec {
config: add CFG_DEFAULT_RUN_TIME for config options with runtime defaults Previously, we declared a default value as undefined ("NULL") for settings which require runtime context to be set first (e.g. settings for paths that rely on SYSTEM_DIR environment variable or they depend on any other setting in some way). If we want to output default values as they are really used in runtime, we should make it possible to define a default value as function which is evaluated, not just providing a firm constant value as it was before. This patch defines simple prototypes for such functions. Also, there's new helper macros "cfg_runtime" and "cfg_array_runtime" - they provide exactly the same functionality as the original "cfg" and "cfg_array" macros when defining the configuration settings in config_settings.h, but they don't set the constant default value. Instead, they automatically link the configuration setting definition with one of these functions: typedef int (*t_fn_CFG_TYPE_BOOL) (struct cmd_context *cmd, struct profile *profile); typedef int (*t_fn_CFG_TYPE_INT) (struct cmd_context *cmd, struct profile *profile); typedef float (*t_fn_CFG_TYPE_FLOAT) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_STRING) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_ARRAY) (struct cmd_context *cmd, struct profile *profile); (The new macros actually set the CFG_DEFAULT_RUNTIME flag properly and set the default value link to the function accordingly). Then such configuration setting requires a function of selected type to be defined. This function has a predefined name: get_default_<id> ...where the <id> is the id of the setting as defined in config_settings.h. For example "backup_archive_dir_CFG" if defined as a setting with default value evaluated in runtime with "cfg_runtime" will automatically have "get_default_backup_archive_dir_CFG" function linked to this setting to get the default value.
2014-03-03 15:34:11 +04:00
struct cmd_context *cmd; /* command context (for run-time defaults */
config: use config checks and add support for creating trees from config definition (config_def_create_tree fn) Configuration checking is initiated during config load/processing (_process_config fn) which is part of the command context creation/refresh. This patch also defines 5 types of trees that could be created from the configuration definition (config_settings.h), the cfg_def_tree_t: - CFG_DEF_TREE_CURRENT that denotes a tree of all the configuration nodes that are explicitly defined in lvm.conf/--config - CFG_DEF_TREE_MISSING that denotes a tree of all missing configuration nodes for which default valus are used since they're not explicitly used in lvm.conf/--config - CFG_DEF_TREE_DEFAULT that denotes a tree of all possible configuration nodes with default values assigned, no matter what the actual lvm.conf/--config is - CFG_DEF_TREE_NEW that denotes a tree of all new configuration nodes that appeared in given version - CFG_DEF_TREE_COMPLETE that denotes a tree of the whole configuration tree that is used in LVM2 (a combination of CFG_DEF_TREE_CURRENT + CFG_DEF_TREE_MISSING). This is not implemented yet, it will be added later... The function that creates the definition tree of given type: struct dm_config_tree *config_def_create_tree(struct config_def_tree_spec *spec); Where the "spec" specifies the tree type to be created: struct config_def_tree_spec { cfg_def_tree_t type; /* tree type */ uint16_t version; /* tree at this LVM2 version */ int ignoreadvanced; /* do not include advanced configs */ int ignoreunsupported; /* do not include unsupported configs */ }; This tree can be passed to already existing functions that write the tree on output (like we already do with cmd->cft). There is a new lvm.conf section called "config" with two new options: - config/checks which enables/disables checking (enabled by default) - config/abort_on_errors which enables/disables aborts on any type of mismatch found in the config (disabled by default)
2013-03-05 20:36:10 +04:00
cfg_def_tree_t type; /* tree type */
uint16_t version; /* tree at this LVM2 version */
dumpconfig: comment out config lines without default values defined To make "lvm dumpconfig --type default" output to be usable like any other config, we need to comment out lines that have no default value defined. Otherwise, we'd have the output with config options with blank or zero values which is not the same as when the value is not defined! And such configuration can't be feed into lvm again without further edits. So let's fix this. Currently this covers these configuration options exactly: devices/loopfiles devices/preferred_names devices/filter devices/global_filter devices/types allocation/cling_tag_list global/format_libraries global/segment_libraries activation/volume_list activation/auto_activation_volume_list activation/read_only_volume_list activation/mlock_filter metadata/dirs metadata/disk_areas metadata/disk_areas/<disk_area> metadata/disk_areas/<disk_area>/start_sector metadata/disk_areas/<disk_area>/size metadata/disk_areas/<disk_area>/id tags/<tag> tags/<tag>/host_list
2014-02-25 14:05:23 +04:00
int ignoreadvanced:1; /* do not include advanced configs */
int ignoreunsupported:1; /* do not include unsupported configs */
int withcomments:1; /* include comments */
int withversions:1; /* include versions */
config: fix use of last config check status if creating CFG_DEF_TREE_MISSING tree When CFG_DEF_TREE_MISSING is created, it needs to know the status of the check done on the tree used (the CFG_USED flag). This bug was introduced with f1c292cc38f4ba2e8d9b7272bc1a1ce17bd729a5 "make it possible to run several instances of configuration check at once". This patch separated the CFG_USED and CFG_VALID flags in a separate 'status' field in struct cft_check_handle. However, when creating some trees, like CFG_DEF_TREE_MISSING, we need this status to do a comparison with full config definition to determine which items are missing and for which default values were used. Otherwise, all items would be considered missing. So, pass this status in a new field called 'check_status' in struct config_def_tree_spec that defines how the (dumpconfig) tree should be constructed (and this struct is passed to config_def_create_tree fn then).
2013-07-08 16:13:09 +04:00
uint8_t *check_status; /* status of last tree check (currently needed for CFG_DEF_TREE_MISSING only) */
config: use config checks and add support for creating trees from config definition (config_def_create_tree fn) Configuration checking is initiated during config load/processing (_process_config fn) which is part of the command context creation/refresh. This patch also defines 5 types of trees that could be created from the configuration definition (config_settings.h), the cfg_def_tree_t: - CFG_DEF_TREE_CURRENT that denotes a tree of all the configuration nodes that are explicitly defined in lvm.conf/--config - CFG_DEF_TREE_MISSING that denotes a tree of all missing configuration nodes for which default valus are used since they're not explicitly used in lvm.conf/--config - CFG_DEF_TREE_DEFAULT that denotes a tree of all possible configuration nodes with default values assigned, no matter what the actual lvm.conf/--config is - CFG_DEF_TREE_NEW that denotes a tree of all new configuration nodes that appeared in given version - CFG_DEF_TREE_COMPLETE that denotes a tree of the whole configuration tree that is used in LVM2 (a combination of CFG_DEF_TREE_CURRENT + CFG_DEF_TREE_MISSING). This is not implemented yet, it will be added later... The function that creates the definition tree of given type: struct dm_config_tree *config_def_create_tree(struct config_def_tree_spec *spec); Where the "spec" specifies the tree type to be created: struct config_def_tree_spec { cfg_def_tree_t type; /* tree type */ uint16_t version; /* tree at this LVM2 version */ int ignoreadvanced; /* do not include advanced configs */ int ignoreunsupported; /* do not include unsupported configs */ }; This tree can be passed to already existing functions that write the tree on output (like we already do with cmd->cft). There is a new lvm.conf section called "config" with two new options: - config/checks which enables/disables checking (enabled by default) - config/abort_on_errors which enables/disables aborts on any type of mismatch found in the config (disabled by default)
2013-03-05 20:36:10 +04:00
};
config: make it possible to run several instances of configuration check at once Before, the status of the configuration check (config_def_check fn call) was saved directly in global configuration definitinion array (as part of the cfg_def_item_t/flags) This patch introduces the "struct cft_check_handle" that defines configuration check parameters as well as separate place to store the status (status here means CFG_USED and CFG_VALID flags, formerly saved in cfg_def_item_t/flags). This struct can hold config check parameters as well as the status for each config tree separately, thus making it possible to run several instances of config_def_check without interference.
2013-06-26 16:53:57 +04:00
/* flag to mark the item as used in a config tree instance during validation */
#define CFG_USED 0x01
/* flag to mark the item as valid in a config tree instance during validation */
#define CFG_VALID 0x02
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
/*
* Register ID for each possible item in the configuration tree.
*/
enum {
#define cfg_section(id, name, parent, flags, since_version, comment) id,
#define cfg(id, name, parent, flags, type, default_value, since_version, comment) id,
config: add CFG_DEFAULT_RUN_TIME for config options with runtime defaults Previously, we declared a default value as undefined ("NULL") for settings which require runtime context to be set first (e.g. settings for paths that rely on SYSTEM_DIR environment variable or they depend on any other setting in some way). If we want to output default values as they are really used in runtime, we should make it possible to define a default value as function which is evaluated, not just providing a firm constant value as it was before. This patch defines simple prototypes for such functions. Also, there's new helper macros "cfg_runtime" and "cfg_array_runtime" - they provide exactly the same functionality as the original "cfg" and "cfg_array" macros when defining the configuration settings in config_settings.h, but they don't set the constant default value. Instead, they automatically link the configuration setting definition with one of these functions: typedef int (*t_fn_CFG_TYPE_BOOL) (struct cmd_context *cmd, struct profile *profile); typedef int (*t_fn_CFG_TYPE_INT) (struct cmd_context *cmd, struct profile *profile); typedef float (*t_fn_CFG_TYPE_FLOAT) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_STRING) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_ARRAY) (struct cmd_context *cmd, struct profile *profile); (The new macros actually set the CFG_DEFAULT_RUNTIME flag properly and set the default value link to the function accordingly). Then such configuration setting requires a function of selected type to be defined. This function has a predefined name: get_default_<id> ...where the <id> is the id of the setting as defined in config_settings.h. For example "backup_archive_dir_CFG" if defined as a setting with default value evaluated in runtime with "cfg_runtime" will automatically have "get_default_backup_archive_dir_CFG" function linked to this setting to get the default value.
2014-03-03 15:34:11 +04:00
#define cfg_runtime(id, name, parent, flags, type, since_version, comment) id,
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
#define cfg_array(id, name, parent, flags, types, default_value, since_version, comment) id,
config: add CFG_DEFAULT_RUN_TIME for config options with runtime defaults Previously, we declared a default value as undefined ("NULL") for settings which require runtime context to be set first (e.g. settings for paths that rely on SYSTEM_DIR environment variable or they depend on any other setting in some way). If we want to output default values as they are really used in runtime, we should make it possible to define a default value as function which is evaluated, not just providing a firm constant value as it was before. This patch defines simple prototypes for such functions. Also, there's new helper macros "cfg_runtime" and "cfg_array_runtime" - they provide exactly the same functionality as the original "cfg" and "cfg_array" macros when defining the configuration settings in config_settings.h, but they don't set the constant default value. Instead, they automatically link the configuration setting definition with one of these functions: typedef int (*t_fn_CFG_TYPE_BOOL) (struct cmd_context *cmd, struct profile *profile); typedef int (*t_fn_CFG_TYPE_INT) (struct cmd_context *cmd, struct profile *profile); typedef float (*t_fn_CFG_TYPE_FLOAT) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_STRING) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_ARRAY) (struct cmd_context *cmd, struct profile *profile); (The new macros actually set the CFG_DEFAULT_RUNTIME flag properly and set the default value link to the function accordingly). Then such configuration setting requires a function of selected type to be defined. This function has a predefined name: get_default_<id> ...where the <id> is the id of the setting as defined in config_settings.h. For example "backup_archive_dir_CFG" if defined as a setting with default value evaluated in runtime with "cfg_runtime" will automatically have "get_default_backup_archive_dir_CFG" function linked to this setting to get the default value.
2014-03-03 15:34:11 +04:00
#define cfg_array_runtime(id, name, parent, flags, types, since_version, comment) id,
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
#include "config_settings.h"
#undef cfg_section
#undef cfg
config: add CFG_DEFAULT_RUN_TIME for config options with runtime defaults Previously, we declared a default value as undefined ("NULL") for settings which require runtime context to be set first (e.g. settings for paths that rely on SYSTEM_DIR environment variable or they depend on any other setting in some way). If we want to output default values as they are really used in runtime, we should make it possible to define a default value as function which is evaluated, not just providing a firm constant value as it was before. This patch defines simple prototypes for such functions. Also, there's new helper macros "cfg_runtime" and "cfg_array_runtime" - they provide exactly the same functionality as the original "cfg" and "cfg_array" macros when defining the configuration settings in config_settings.h, but they don't set the constant default value. Instead, they automatically link the configuration setting definition with one of these functions: typedef int (*t_fn_CFG_TYPE_BOOL) (struct cmd_context *cmd, struct profile *profile); typedef int (*t_fn_CFG_TYPE_INT) (struct cmd_context *cmd, struct profile *profile); typedef float (*t_fn_CFG_TYPE_FLOAT) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_STRING) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_ARRAY) (struct cmd_context *cmd, struct profile *profile); (The new macros actually set the CFG_DEFAULT_RUNTIME flag properly and set the default value link to the function accordingly). Then such configuration setting requires a function of selected type to be defined. This function has a predefined name: get_default_<id> ...where the <id> is the id of the setting as defined in config_settings.h. For example "backup_archive_dir_CFG" if defined as a setting with default value evaluated in runtime with "cfg_runtime" will automatically have "get_default_backup_archive_dir_CFG" function linked to this setting to get the default value.
2014-03-03 15:34:11 +04:00
#undef cfg_runtime
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
#undef cfg_array
config: add CFG_DEFAULT_RUN_TIME for config options with runtime defaults Previously, we declared a default value as undefined ("NULL") for settings which require runtime context to be set first (e.g. settings for paths that rely on SYSTEM_DIR environment variable or they depend on any other setting in some way). If we want to output default values as they are really used in runtime, we should make it possible to define a default value as function which is evaluated, not just providing a firm constant value as it was before. This patch defines simple prototypes for such functions. Also, there's new helper macros "cfg_runtime" and "cfg_array_runtime" - they provide exactly the same functionality as the original "cfg" and "cfg_array" macros when defining the configuration settings in config_settings.h, but they don't set the constant default value. Instead, they automatically link the configuration setting definition with one of these functions: typedef int (*t_fn_CFG_TYPE_BOOL) (struct cmd_context *cmd, struct profile *profile); typedef int (*t_fn_CFG_TYPE_INT) (struct cmd_context *cmd, struct profile *profile); typedef float (*t_fn_CFG_TYPE_FLOAT) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_STRING) (struct cmd_context *cmd, struct profile *profile); typedef const char* (*t_fn_CFG_TYPE_ARRAY) (struct cmd_context *cmd, struct profile *profile); (The new macros actually set the CFG_DEFAULT_RUNTIME flag properly and set the default value link to the function accordingly). Then such configuration setting requires a function of selected type to be defined. This function has a predefined name: get_default_<id> ...where the <id> is the id of the setting as defined in config_settings.h. For example "backup_archive_dir_CFG" if defined as a setting with default value evaluated in runtime with "cfg_runtime" will automatically have "get_default_backup_archive_dir_CFG" function linked to this setting to get the default value.
2014-03-03 15:34:11 +04:00
#undef cfg_array_runtime
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
};
config: add support for loading profiles This patch adds --profile arg to lvm cmds and adds config/profile_dir configuration setting to select the directory where profiles are stored By default it's /etc/lvm/profile. The profiles are added by using new "add_profile" fn and then loaded using the "load_profile" fn. All profiles are stored in a cmd context within the new "struct profile_params": struct profile_params { const char *dir; struct profile *global_profile; struct dm_list profiles_to_load; struct dm_list profiles; }; ...where "dir" is the directory with profiles, "global_profile" is the profile that is set globally via the --profile arg (IOW, not set per VG/LV basis based on metadata record) and the "profiles" is the list with loaded profiles.
2013-06-25 14:27:04 +04:00
struct profile *add_profile(struct cmd_context *cmd, const char *profile_name);
int load_profile(struct cmd_context *cmd, struct profile *profile);
int load_pending_profiles(struct cmd_context *cmd);
config: make it possible to run several instances of configuration check at once Before, the status of the configuration check (config_def_check fn call) was saved directly in global configuration definitinion array (as part of the cfg_def_item_t/flags) This patch introduces the "struct cft_check_handle" that defines configuration check parameters as well as separate place to store the status (status here means CFG_USED and CFG_VALID flags, formerly saved in cfg_def_item_t/flags). This struct can hold config check parameters as well as the status for each config tree separately, thus making it possible to run several instances of config_def_check without interference.
2013-06-26 16:53:57 +04:00
/* configuration check handle for each instance of the validation check */
struct cft_check_handle {
struct dm_config_tree *cft; /* the tree for which the check is done */
config: add validation for configuration profiles Besides the classical configuration checks (type checking and checking whether the item is recognized by lvm tools) for profiles, do an extra check whether the configuration setting is customizable by a profile at all. Give a warning message if not.
2013-06-26 18:27:28 +04:00
config_source_t source; /* configuration source */
config: make it possible to run several instances of configuration check at once Before, the status of the configuration check (config_def_check fn call) was saved directly in global configuration definitinion array (as part of the cfg_def_item_t/flags) This patch introduces the "struct cft_check_handle" that defines configuration check parameters as well as separate place to store the status (status here means CFG_USED and CFG_VALID flags, formerly saved in cfg_def_item_t/flags). This struct can hold config check parameters as well as the status for each config tree separately, thus making it possible to run several instances of config_def_check without interference.
2013-06-26 16:53:57 +04:00
unsigned force_check:1; /* force check even if disabled by config/checks setting */
unsigned skip_if_checked:1; /* skip the check if already done before - return last state */
unsigned suppress_messages:1; /* suppress messages during the check if config item is found invalid */
uint8_t status[CFG_COUNT]; /* flags for each configuration item - the result of the check */
};
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
int config_def_get_path(char *buf, size_t buf_size, int id);
config: make it possible to run several instances of configuration check at once Before, the status of the configuration check (config_def_check fn call) was saved directly in global configuration definitinion array (as part of the cfg_def_item_t/flags) This patch introduces the "struct cft_check_handle" that defines configuration check parameters as well as separate place to store the status (status here means CFG_USED and CFG_VALID flags, formerly saved in cfg_def_item_t/flags). This struct can hold config check parameters as well as the status for each config tree separately, thus making it possible to run several instances of config_def_check without interference.
2013-06-26 16:53:57 +04:00
int config_def_check(struct cmd_context *cmd, struct cft_check_handle *handle);
config: add structs to represent config definition and register config_settings.h content This patch adds basic structures that encapsulate the config_settings.h content - it takes each item and puts it in structures: - cfg_def_type_t to define config item type - cfg_def_value_t to define config item (default) value - flags used to define the nature and use of the config item: - CFG_NAME_VARIABLE for items with variable names (e.g. tags) - CFG_ALLOW_EMPTY for items where empty value is allowed - CFG_ADVANCED for items which are considered as "advanced settings" - CFG_UNSUPPORTED for items which are not officially supported (config options mostly for internal use and testing/debugging) - cfg_def_item_t to encapsulate the whole definition of the config definition itself Each config item is referenced by named ID, e.g. "devices_dir_CFG" instead of directly typing the path "devices/dir" as it was before. This patch also adds cfg_def_get_path helper function to get the config setting path up to the root for given config ID (it returns the path in form of "abc/def/.../xyz" where the "abc" is the topmost element).
2013-03-05 19:49:42 +04:00
config: add config_source_t type to identify configuration source A helper type that helps with identification of the configuration source which makes handling the configuration cascade a bit easier, mainly removing and adding configuration trees to cascade dynamically. Currently, the possible types are: CONFIG_UNDEFINED - configuration is not defined yet (not initialized) CONFIG_FILE - one file configuration CONFIG_MERGED_FILES - configuration that is a result of merging more files into one CONFIG_STRING - configuration string typed on cmd line directly CONFIG_PROFILE - profile configuration (the new type of configuration, patches will follow...) Also, generalize existing "remove_overridden_config_tree" to work with configuration type identification in a cascade. Before, it was just the CONFIG_STRING we used. Now, we need some more to add in a cascade (like the CONFIG_PROFILE). So, we have: struct dm_config_tree *remove_config_tree_by_source(struct cmd_context *cmd, config_source_t source); config_source_t config_get_source_type(struct dm_config_tree *cft); ... for removing the tree by its source type from the cascade and simply getting the source type.
2013-06-25 14:25:43 +04:00
int override_config_tree_from_string(struct cmd_context *cmd, const char *config_settings);
config: add override_config_tree_from_profile fn to add the profile to a configuration cascade When placing the profile in a configuration cascade, this sequence is used exactly: CONFIG_STRING -> CONFIG_PROFILE -> CONFIG_FILE/MERGED_FILES So if the profile is used, it overloads the lvm.conf (and any existing tag configs). However, if "--config" is used to define a custom configuration on command line, this overloads even the profile config!
2013-06-25 14:27:37 +04:00
int override_config_tree_from_profile(struct cmd_context *cmd, struct profile *profile);
config: add config_source_t type to identify configuration source A helper type that helps with identification of the configuration source which makes handling the configuration cascade a bit easier, mainly removing and adding configuration trees to cascade dynamically. Currently, the possible types are: CONFIG_UNDEFINED - configuration is not defined yet (not initialized) CONFIG_FILE - one file configuration CONFIG_MERGED_FILES - configuration that is a result of merging more files into one CONFIG_STRING - configuration string typed on cmd line directly CONFIG_PROFILE - profile configuration (the new type of configuration, patches will follow...) Also, generalize existing "remove_overridden_config_tree" to work with configuration type identification in a cascade. Before, it was just the CONFIG_STRING we used. Now, we need some more to add in a cascade (like the CONFIG_PROFILE). So, we have: struct dm_config_tree *remove_config_tree_by_source(struct cmd_context *cmd, config_source_t source); config_source_t config_get_source_type(struct dm_config_tree *cft); ... for removing the tree by its source type from the cascade and simply getting the source type.
2013-06-25 14:25:43 +04:00
struct dm_config_tree *remove_config_tree_by_source(struct cmd_context *cmd, config_source_t source);
config_source_t config_get_source_type(struct dm_config_tree *cft);
o Populating with stuff from experimental
2001-08-21 16:56:08 +04:00
Speed up CRC32 calculations by using a larger lookup table. Use -DDEBUG_CRC32 to revert to old function and check new one gives same result.
2010-09-27 23:09:34 +04:00
typedef uint32_t (*checksum_fn_t) (uint32_t initial, const uint8_t *buf, uint32_t size);
Refactoring.
2002-11-18 17:01:16 +03:00
config: add config_source_t type to identify configuration source A helper type that helps with identification of the configuration source which makes handling the configuration cascade a bit easier, mainly removing and adding configuration trees to cascade dynamically. Currently, the possible types are: CONFIG_UNDEFINED - configuration is not defined yet (not initialized) CONFIG_FILE - one file configuration CONFIG_MERGED_FILES - configuration that is a result of merging more files into one CONFIG_STRING - configuration string typed on cmd line directly CONFIG_PROFILE - profile configuration (the new type of configuration, patches will follow...) Also, generalize existing "remove_overridden_config_tree" to work with configuration type identification in a cascade. Before, it was just the CONFIG_STRING we used. Now, we need some more to add in a cascade (like the CONFIG_PROFILE). So, we have: struct dm_config_tree *remove_config_tree_by_source(struct cmd_context *cmd, config_source_t source); config_source_t config_get_source_type(struct dm_config_tree *cft); ... for removing the tree by its source type from the cascade and simply getting the source type.
2013-06-25 14:25:43 +04:00
struct dm_config_tree *config_open(config_source_t source, const char *filename, int keep_open);
Make a cleaner split between config tree and config file functionality. Move the latter out of libdm.
2011-12-19 01:56:03 +04:00
int config_file_read_fd(struct dm_config_tree *cft, struct device *dev,
off_t offset, size_t size, off_t offset2, size_t size2,
checksum_fn_t checksum_fn, uint32_t checksum);
cleanup: indent line
2013-01-19 15:04:17 +04:00
int config_file_read(struct dm_config_tree *cft);
config: add config_source_t type to identify configuration source A helper type that helps with identification of the configuration source which makes handling the configuration cascade a bit easier, mainly removing and adding configuration trees to cascade dynamically. Currently, the possible types are: CONFIG_UNDEFINED - configuration is not defined yet (not initialized) CONFIG_FILE - one file configuration CONFIG_MERGED_FILES - configuration that is a result of merging more files into one CONFIG_STRING - configuration string typed on cmd line directly CONFIG_PROFILE - profile configuration (the new type of configuration, patches will follow...) Also, generalize existing "remove_overridden_config_tree" to work with configuration type identification in a cascade. Before, it was just the CONFIG_STRING we used. Now, we need some more to add in a cascade (like the CONFIG_PROFILE). So, we have: struct dm_config_tree *remove_config_tree_by_source(struct cmd_context *cmd, config_source_t source); config_source_t config_get_source_type(struct dm_config_tree *cft); ... for removing the tree by its source type from the cascade and simply getting the source type.
2013-06-25 14:25:43 +04:00
struct dm_config_tree *config_file_open_and_read(const char *config_file, config_source_t source);
dumpconfig: comment out config lines without default values defined To make "lvm dumpconfig --type default" output to be usable like any other config, we need to comment out lines that have no default value defined. Otherwise, we'd have the output with config options with blank or zero values which is not the same as when the value is not defined! And such configuration can't be feed into lvm again without further edits. So let's fix this. Currently this covers these configuration options exactly: devices/loopfiles devices/preferred_names devices/filter devices/global_filter devices/types allocation/cling_tag_list global/format_libraries global/segment_libraries activation/volume_list activation/auto_activation_volume_list activation/read_only_volume_list activation/mlock_filter metadata/dirs metadata/disk_areas metadata/disk_areas/<disk_area> metadata/disk_areas/<disk_area>/start_sector metadata/disk_areas/<disk_area>/size metadata/disk_areas/<disk_area>/id tags/<tag> tags/<tag>/host_list
2014-02-25 14:05:23 +04:00
int config_write(struct dm_config_tree *cft, struct config_def_tree_spec *tree_spec,
dumpconfig: add --withcomments and --withversions switch lvm dumpconfig [--withcomments] [--withversions] The --withcomments causes the comments to appear on output before each config node (if they were defined in config_settings.h). The --withversions causes a one line extra comment to appear on output before each config node with the version information in which the configuration setting first appeared.
2013-03-05 21:21:13 +04:00
const char *file, int argc, char **argv);
config: use config checks and add support for creating trees from config definition (config_def_create_tree fn) Configuration checking is initiated during config load/processing (_process_config fn) which is part of the command context creation/refresh. This patch also defines 5 types of trees that could be created from the configuration definition (config_settings.h), the cfg_def_tree_t: - CFG_DEF_TREE_CURRENT that denotes a tree of all the configuration nodes that are explicitly defined in lvm.conf/--config - CFG_DEF_TREE_MISSING that denotes a tree of all missing configuration nodes for which default valus are used since they're not explicitly used in lvm.conf/--config - CFG_DEF_TREE_DEFAULT that denotes a tree of all possible configuration nodes with default values assigned, no matter what the actual lvm.conf/--config is - CFG_DEF_TREE_NEW that denotes a tree of all new configuration nodes that appeared in given version - CFG_DEF_TREE_COMPLETE that denotes a tree of the whole configuration tree that is used in LVM2 (a combination of CFG_DEF_TREE_CURRENT + CFG_DEF_TREE_MISSING). This is not implemented yet, it will be added later... The function that creates the definition tree of given type: struct dm_config_tree *config_def_create_tree(struct config_def_tree_spec *spec); Where the "spec" specifies the tree type to be created: struct config_def_tree_spec { cfg_def_tree_t type; /* tree type */ uint16_t version; /* tree at this LVM2 version */ int ignoreadvanced; /* do not include advanced configs */ int ignoreunsupported; /* do not include unsupported configs */ }; This tree can be passed to already existing functions that write the tree on output (like we already do with cmd->cft). There is a new lvm.conf section called "config" with two new options: - config/checks which enables/disables checking (enabled by default) - config/abort_on_errors which enables/disables aborts on any type of mismatch found in the config (disabled by default)
2013-03-05 20:36:10 +04:00
struct dm_config_tree *config_def_create_tree(struct config_def_tree_spec *spec);
config: add config_source_t type to identify configuration source A helper type that helps with identification of the configuration source which makes handling the configuration cascade a bit easier, mainly removing and adding configuration trees to cascade dynamically. Currently, the possible types are: CONFIG_UNDEFINED - configuration is not defined yet (not initialized) CONFIG_FILE - one file configuration CONFIG_MERGED_FILES - configuration that is a result of merging more files into one CONFIG_STRING - configuration string typed on cmd line directly CONFIG_PROFILE - profile configuration (the new type of configuration, patches will follow...) Also, generalize existing "remove_overridden_config_tree" to work with configuration type identification in a cascade. Before, it was just the CONFIG_STRING we used. Now, we need some more to add in a cascade (like the CONFIG_PROFILE). So, we have: struct dm_config_tree *remove_config_tree_by_source(struct cmd_context *cmd, config_source_t source); config_source_t config_get_source_type(struct dm_config_tree *cft); ... for removing the tree by its source type from the cascade and simply getting the source type.
2013-06-25 14:25:43 +04:00
void config_destroy(struct dm_config_tree *cft);
Make a cleaner split between config tree and config file functionality. Move the latter out of libdm.
2011-12-19 01:56:03 +04:00
time_t config_file_timestamp(struct dm_config_tree *cft);
int config_file_changed(struct dm_config_tree *cft);
int config_file_check(struct dm_config_tree *cft, const char **filename, struct stat *info);
Move dm_config_write out of libdm, back to lib/config, as config_write.
2011-12-12 03:18:20 +04:00
Handle metadata with unknown segment types more gracefully.
2009-10-16 21:41:49 +04:00
config: make it possible to do a raw config tree merge Till now, we needed the config tree merge only for merging tag configs with lvm.conf. However, this type of merging did a few extra exceptions: - leaving out the tags section - merging values in activation/volume_list - merging values in devices/filter - merging values in devices/types Any other config values were replaced by new values. However, we'd like to do a 'raw merge' as well, simply bypassing the exceptions listed above. This will help us to create a single tree representing the cascaded configs like CONFIG_STRING -> CONFIG_PROFILE -> ... The reason for this patch is that when trees are cascaded, the first value found while traversing the cascade is used, not making any exceptions like we do for tag configs.
2013-07-08 16:31:44 +04:00
typedef enum {
CONFIG_MERGE_TYPE_RAW, /* always replace old config values with new config values when merging */
CONFIG_MERGE_TYPE_TAGS /* apply some exceptions when merging tag configs:
- skip tags section
- do not replace, but merge values of these settings:
activation/volume_list
devices/filter
devices/types
*/
} config_merge_t;
Move the core of the lib/config/config.c functionality into libdevmapper, leaving behind the LVM-specific parts of the code (convenience wrappers that handle `struct device` and `struct cmd_context`, basically). A number of functions have been renamed (in addition to getting a dm_ prefix) -- namely, all of the config interface now has a dm_config_ prefix.
2011-08-30 18:55:15 +04:00
int merge_config_tree(struct cmd_context *cmd, struct dm_config_tree *cft,
config: make it possible to do a raw config tree merge Till now, we needed the config tree merge only for merging tag configs with lvm.conf. However, this type of merging did a few extra exceptions: - leaving out the tags section - merging values in activation/volume_list - merging values in devices/filter - merging values in devices/types Any other config values were replaced by new values. However, we'd like to do a 'raw merge' as well, simply bypassing the exceptions listed above. This will help us to create a single tree representing the cascaded configs like CONFIG_STRING -> CONFIG_PROFILE -> ... The reason for this patch is that when trees are cascaded, the first value found while traversing the cascade is used, not making any exceptions like we do for tag configs.
2013-07-08 16:31:44 +04:00
struct dm_config_tree *newdata, config_merge_t);
o Populating with stuff from experimental
2001-08-21 16:56:08 +04:00
Fix lvcreate corelog validation. Add --config for overriding most config file settings from cmdline. Quote arguments when printing command line. Remove linefeed from 'initialising logging' message. Add 'Completed' debug message. Don't attempt library exit after reloading config files. Always compile with libdevmapper, even if device-mapper is disabled.
2006-05-16 20:48:31 +04:00
/*
* These versions check an override tree, if present, first.
*/
config: add profile arg to find_config_tree_node
2013-06-25 14:29:33 +04:00
const struct dm_config_node *find_config_tree_node(struct cmd_context *cmd, int id, struct profile *profile);
config: add profile arg to find_config_tree_str
2013-06-25 14:29:54 +04:00
const char *find_config_tree_str(struct cmd_context *cmd, int id, struct profile *profile);
config: add profile arg to find_config_tree_str_allow_empty
2013-06-25 14:30:08 +04:00
const char *find_config_tree_str_allow_empty(struct cmd_context *cmd, int id, struct profile *profile);
config: add profile arg to find_config_tree_int
2013-06-25 14:30:34 +04:00
int find_config_tree_int(struct cmd_context *cmd, int id, struct profile *profile);
config: add profile arg to find_config_tree_int64
2013-06-25 14:31:24 +04:00
int64_t find_config_tree_int64(struct cmd_context *cmd, int id, struct profile *profile);
config: add profile arg to find_config_tree_float
2013-06-25 14:31:36 +04:00
float find_config_tree_float(struct cmd_context *cmd, int id, struct profile *profile);
config: add profile arg to find_config_tree_bool
2013-06-25 14:31:53 +04:00
int find_config_tree_bool(struct cmd_context *cmd, int id, struct profile *profile);
Add 'get' functions.
2002-01-10 19:47:58 +03:00
config: runtime default for devices/cache, devices/cache_dir The devices/cache and devices/cache_dir are evaluated in runtime this way: - if devices/cache is set, use it - if devices_cache/dir or devices/cache_file_prefix is set, make up a path out of that for devices/cache in runtime, taking into account the LVM_SYSTEM_DIR environment variable if set - otherwise make up the path out of default which is: <LVM_SYSTEM_DIR>/<cache_dir>/<cache_file_prefix>.cache With the runtime defaults, we can encode this easily now. Also, the lvm dumpconfig can show proper and exact information about this setting then (the variant that shows default values).
2014-03-03 15:47:32 +04:00
/*
config: runtime default for backup/backup_dir, backup/archive_dir The backup/backup_dir and backup/archive_dir default value is evaluated in runtime and takes LVM_SYSTEM_DIR into consideration...
2014-03-03 16:24:30 +04:00
* Functions for configuration settings for which the default
* value is evaluated at runtime based on command context.
config: runtime default for devices/cache, devices/cache_dir The devices/cache and devices/cache_dir are evaluated in runtime this way: - if devices/cache is set, use it - if devices_cache/dir or devices/cache_file_prefix is set, make up a path out of that for devices/cache in runtime, taking into account the LVM_SYSTEM_DIR environment variable if set - otherwise make up the path out of default which is: <LVM_SYSTEM_DIR>/<cache_dir>/<cache_file_prefix>.cache With the runtime defaults, we can encode this easily now. Also, the lvm dumpconfig can show proper and exact information about this setting then (the variant that shows default values).
2014-03-03 15:47:32 +04:00
*/
const char *get_default_devices_cache_dir_CFG(struct cmd_context *cmd, struct profile *profile);
const char *get_default_devices_cache_CFG(struct cmd_context *cmd, struct profile *profile);
config: runtime default for backup/backup_dir, backup/archive_dir The backup/backup_dir and backup/archive_dir default value is evaluated in runtime and takes LVM_SYSTEM_DIR into consideration...
2014-03-03 16:24:30 +04:00
const char *get_default_backup_backup_dir_CFG(struct cmd_context *cmd, struct profile *profile);
const char *get_default_backup_archive_dir_CFG(struct cmd_context *cmd, struct profile *profile);
config: runtime default for config/profile_dir The config/profile_dir default value takes LVM_SYSTEM_DIR into consideraton.
2014-03-03 16:30:13 +04:00
const char *get_default_config_profile_dir_CFG(struct cmd_context *cmd, struct profile *profile);
config: runtime default for activation/mirror_image_fault_policy The activation/mirror_image_fault_policy default value copies the value (or default one) used for activation/mirror_device_fault_policy.
2014-03-03 16:37:35 +04:00
const char *get_default_activation_mirror_image_fault_policy_CFG(struct cmd_context *cmd, struct profile *profile);
config: runtime default for allocation/thin_pool_chunk_size The allocation/thin_pool_chunk_size is a bit more complex. It's default value is evaluated in runtime based on selected thin_pool_chunk_size_policy. But the value is just a starting point. The calculation then continues with dependency on the properties of the devices used. Which means for such a default value, we know only the starting value.
2014-03-04 14:10:59 +04:00
int get_default_allocation_thin_pool_chunk_size_CFG(struct cmd_context *cmd, struct profile *profile);
config: add default for allocation/cache_pool_chunk_size The same as for allocation/thin_pool_chunk_size - the default value used is just a starting point. The calculation continues using the properties of the devices actually used.
2014-03-04 14:15:54 +04:00
int get_default_allocation_cache_pool_chunk_size_CFG(struct cmd_context *cmd, struct profile *profile);
config: runtime default for devices/cache, devices/cache_dir The devices/cache and devices/cache_dir are evaluated in runtime this way: - if devices/cache is set, use it - if devices_cache/dir or devices/cache_file_prefix is set, make up a path out of that for devices/cache in runtime, taking into account the LVM_SYSTEM_DIR environment variable if set - otherwise make up the path out of default which is: <LVM_SYSTEM_DIR>/<cache_dir>/<cache_file_prefix>.cache With the runtime defaults, we can encode this easily now. Also, the lvm dumpconfig can show proper and exact information about this setting then (the variant that shows default values).
2014-03-03 15:47:32 +04:00
o Populating with stuff from experimental
2001-08-21 16:56:08 +04:00
#endif
Copy Permalink