4 Commits

Author	SHA1	Message	Date
Peter Rajnoha	d169ff1e03	conf: add report/list_item_separator lvm.conf option ... For example: $ lvm dumpconfig report/list_item_separator list_item_separator="," $ lvs -o name,tags vg/lvol1 LV LV Tags lvol1 a,x,y $ lvm dumpconfig report/list_item_separator list_item_separator=":" $ lvs -o name,tags vg/lvol1 LV LV Tags lvol1 a❌y	2014-07-10 16:18:45 +02:00
Peter Rajnoha	fafd10d564	conf: command_profile_template: global/binary_values_as_numeric -> report/binary_values_as_numeric	2014-07-10 09:48:45 +02:00
Peter Rajnoha	da545ce3b4	tools: add --binary arg to pvs,vgs,lvs and {pv,vg,lv}display -C and report/binary_values_as_numeric lvm.conf option ... The --binary option, if used, causes all the binary values reported in reporting commands to be displayed as "0" or "1" instead of descriptive literal values (value "unknown" is still used for values that could not be determined). Also, add report/binary_values_as_numeric lvm.conf option with the same functionality as the --binary option (the --binary option prevails if both --binary cmd option and report/binary_values_as_numeric lvm.conf option is used at the same time). The report/binary_values_as_numeric is also profilable. This makes it easier to use and check lvm reporting command output in scripts.	2014-07-04 15:40:17 +02:00
Peter Rajnoha	23f9c45a1b	profiles: remove default.profile and add {command,metadata}_profile_template.profile ... The "default.profile" name was misleading. It's actually a helper *template* that can be used for copying and further editing to create a new profile. Also, we have separate command and metadata profiles now so the templates are separated as well - we can't mix profile settings from one group with another - such profile is rejected by lvm tools.	2014-05-21 12:36:52 +02:00