summaryrefslogtreecommitdiffstats
path: root/scripts/lvm2_monitoring_init_red_hat.in
Commit message (Collapse)AuthorAgeFilesLines
* Use also normalized output for vgchange command in lvm2-monitor init script.Peter Rajnoha2011-12-161-2/+2
|
* Fix lvm2-monitor init script to use normalized output when using vgs.Peter Rajnoha2011-12-071-2/+2
|
* Suppress locking error messages in monitoring init scripts.Peter Rajnoha2011-08-111-0/+1
|
* Change daemon lock filename from lvm2_monitor to lvm2-monitor for consistency.Alasdair Kergon2010-04-151-1/+1
|
* Add a [--poll {y|n}] flag to vgchange and lvchange to control whetherMike Snitzer2010-01-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | 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>
* drop -ing suffixAlasdair Kergon2009-09-161-2/+2
|
* Update lvm2_monitoring script.Alasdair Kergon2009-09-161-0/+119