~registry/lvm2/master : changes

~registry/lvm2/master » Changes to configure.in from revision 7316

From Revision 7316 to 6485

Rev	Summary	Authors	Date
7130	scripts: introduce blkdeactivate scripts: introduce blkdeactivate blkdeactivate - utility to deactivate block devices Traverses the tree of block devices and tries to deactivate them. Currently, it supports device-mapper-based devices together with LVM. See man/blkdeactivate.8 for more info. It is targeted for use during shutdown to properly deactivate the whole block device stack - systemd and init scripts are provided as well. However, it might be used directly on command line too. Please, see the commentary at the top of the blkdeactivate script for dependencies and versions of other utilities required.	Peter Rajnoha	12 years ago
7117	python: Add bindings for liblvm2app. python: Add bindings for liblvm2app. Use configure --enable-python_bindings to generate them. Note that the Makefiles do not yet control the owner or permissions of the two new files on installation.	Alasdair G Kergon	12 years ago
7083	configure: Use pkg-config to look for valgrind/memcheck.h. configure: Use pkg-config to look for valgrind/memcheck.h.	Petr Rockai	12 years ago
7040	configure: fix --enable-testing configure: fix --enable-testing Add missing pkg init for configure --enable-testing.	Zdenek Kabelac	12 years ago
6927	systemd: integrate lvm2 activation generator with conf+make systemd: integrate lvm2 activation generator with conf+make	Peter Rajnoha	12 years ago
6893	configure: default tmpfile dir in PREFIX/lib/tmpfiles.d configure: default tmpfile dir in PREFIX/lib/tmpfiles.d SYSCONFDIR (the /etc) contains overrides to system-wide settings. System-wide settings are in PREFIX/lib/tmpfiles.d by default	Peter Rajnoha	12 years ago
6867	udev: udev rules cleanup udev: udev rules cleanup Remove executable path detection in udev rules and use sbindir that is configured, but still provide the original functionality by means of 'configure --enable-udev-rule-exec-detection'. Normally, the exec path for the tools called in udev rules should not differ from the sbindir used, however, there are cases this is necessary. For example different environments could be assembled in a way that these path differ for some reason (distribution installer, initrd ...). This functionality is kept for compatibility only. Any environment moving the binaries around and using different paths should be fixed eventually!	Peter Rajnoha	12 years ago
6866	configure: run directory configuration cleanup configure: run directory configuration cleanup There were several hard-coded values for run directory around the code. Also, some tools are DM specific only, others are LVM specific and there was no distinction made here before. With this patch applied, we have this cleaned up a bit (subsystem in brackets, defaults in parentheses): [common] configurable PID_DIR (/var/run) lvm [lvm] configurable RUN_DIR (/var/run/lvm) configurable locking dir (/var/lock/lvm) clvmd [lvm] configurable pid file (PID_DIR/clvmd.pid) socket (RUN_DIR/clvmd.sock) lvmetad [lvm] configurable pid file (PID_DIR/lvmetad.pid) socket (RUN_DIR/lvmetad.socket) dm [dm] configurable DM_RUN_DIR (/var/run) cmirrord [dm] configurable pid file (PID_DIR/cmirrord.pid) dmeventd [dm] configurable pid file (PID_DIR/dmeventd.pid) server fifo (DM_RUN_DIR/dmeventd-server) client fifo (DM_RUN_DIR/dmeventd-client) The changes briefly: - added configure --with-default-pid-dir - added configure --with-default-dm-run-dir - added configure --with-lvmetad-pidfile - by default, using one common pid directory for everything (only lvmetad was not following this before)	Peter Rajnoha	12 years ago
6849	veritysetup: Remove code as now in cryptsetup. veritysetup: Remove code as now in cryptsetup. The veritysetup code has moved to the cryptsetup package. http://code.google.com/p/cryptsetup/	Alasdair G Kergon	12 years ago
6809	Add missing pkg init Add missing pkg init	Zdenek Kabelac	12 years ago
6748	Rename verity dir Rename verity dir	Alasdair Kergon	12 years ago
6742	First veritysetup version using configure --with-veritysetup... First veritysetup version using configure --with-veritysetup.	Alasdair Kergon	12 years ago
6707	Update configure change Update configure change Always define THIN_CHECK_CMD define - since for now we compile thin code in more places.	Zdenek Kabelac	12 years ago
6702	Add --with-thin-check configure option Add --with-thin-check configure option If specified - use given path without test (Path could be empty) If autodetection is in use - check for command in available PATH.	Zdenek Kabelac	12 years ago
6600	Allow cluster mirrors to handle the absence of the checkpoin... Allow cluster mirrors to handle the absence of the checkpoint lib (libSaCkpt). The OpenAIS checkpoint library is going away; therefore, cmirrord must operate without it. The algorithms the handle the timing of when to send a checkpoint, the determination of what to send, and which ongoing cluster requests are relevent with respect to the checkpoints are unaffected. We need only replace the functions that actually perform the storing/transmitting and retrieving/receiving of the checkpoint data. Rather than store the checkpoint data in an OpenAIS checkpoint file, we simply transmit it along with the message that notifies the incoming node that the checkpoint is ready.	Jonathan Earl Brasso...	12 years ago
6586	Define LVMETAD_SUPPORT in source code Define LVMETAD_SUPPORT in source code	Alasdair Kergon	12 years ago
6526	Add LVMetaD init script. Add LVMetaD init script.	Peter Rajnoha	12 years ago
6496	Use DEFAULT_RUN_DIR instead of hardcoded value in lvmetad sy... Use DEFAULT_RUN_DIR instead of hardcoded value in lvmetad systemd units and add ExecStartPost=vgscan to actually run the first scan that will fill the metadata daemon with metadata information.	Peter Rajnoha	12 years ago
6491	Add LVMetaD systemd units. Add LVMetaD systemd units.	Peter Rajnoha	12 years ago
6485	Add configure --with-tmpfilesdir and lvm2 tmpfiles.d configu... Add configure --with-tmpfilesdir and lvm2 tmpfiles.d configuration file itself. /etc/tmpfiles.d directory holds configuration files for temporary/volatile files and directories that should be automatically managed. For example, if we have some parts of the fs hierarchy on tmpfs, we'd like to recreate some files or directories on every boot so they're always prepared for use. Systemd can read such configuration files. For now, the lock and run directory are the ones that are most probably placed on tmpfs. If this is the case, we can install the configuration by 'make install_tmpfiles_configuration'.	Peter Rajnoha	12 years ago

Older »