8 Commits

Author	SHA1	Message	Date
Peter Rajnoha	f33a224ef0	scripts: use --ignoreskippedcluster in lvm2-monitor initscript/systemd unit ... When clustered VG is available in the system but we don't have clustering set up for whatever reason, the lvm2-monitor scripts should not fail completely just because these clustered VGs are skipped during vgs/vgchange calls in lvm2-monitor initscript/systemd unit.	2014-02-17 16:29:49 +01:00
Peter Rajnoha	32e53e506d	Use also normalized output for vgchange command in lvm2-monitor init script.	2011-12-16 11:42:56 +00:00
Peter Rajnoha	0644371f09	Fix lvm2-monitor init script to use normalized output when using vgs.	2011-12-07 12:29:41 +00:00
Peter Rajnoha	d183554c72	Suppress locking error messages in monitoring init scripts.	2011-08-11 15:27:46 +00:00
Alasdair Kergon	81182ac07a	Change daemon lock filename from lvm2_monitor to lvm2-monitor for consistency.	2010-04-15 19:15:03 +00:00
Mike Snitzer	7a8fa6aaab	Add a [--poll {y|n}] flag to vgchange and lvchange to control whether ... the background polldaemon is allowed to start. It can be used standalone or in conjunction with --refresh or --available y. Control over when the background polldaemon starts will be particularly important for snapshot-merge of a root filesystem. Dracut will be updated to activate all LVs with: --poll n The lvm2-monitor initscript will start polling with: --poll y NOTE: Because we currently have no way of knowing if a background polldaemon is active for a given LV the following limitations exist and have been deemed acceptable: 1) it is not possible to stop an active polldaemon; so the lvm2-monitor initscript doesn't stop running polldaemon(s) 2) redundant polldaemon instances will be started for all specified LVs if vgchange or lvchange are repeatedly used with '--poll y' Signed-off-by: Mike Snitzer <snitzer@redhat.com>	2010-01-05 20:56:51 +00:00
Alasdair Kergon	0c29b5cb89	drop -ing suffix	2009-09-16 23:40:19 +00:00
Alasdair Kergon	595eaf925c	Update lvm2_monitoring script.	2009-09-16 23:22:40 +00:00