diff options
| author | Dave Wysochanski <dwysocha@redhat.com> | 2008-12-18 05:27:17 +0000 |
|---|---|---|
| committer | Dave Wysochanski <dwysocha@redhat.com> | 2008-12-18 05:27:17 +0000 |
| commit | 02961979994ceb2ce2e38f79ea4b5719faf3fb42 (patch) | |
| tree | 7177cffb185d8317bf8a5e1120562024c71b3a88 /daemons/clvmd/lvm-functions.c | |
| parent | c5c13fe77627ef0329d1022c6b3daab99decd258 (diff) | |
| download | lvm2-02961979994ceb2ce2e38f79ea4b5719faf3fb42.tar.gz lvm2-02961979994ceb2ce2e38f79ea4b5719faf3fb42.tar.xz lvm2-02961979994ceb2ce2e38f79ea4b5719faf3fb42.zip | |
Create global is_static() to eliminate from the library init function.
Very simple / crude method of removing 'is_static' from initialization.
Why should we require an application tell us whether it is linked
statically or dynamically to libLVM? If the application is linked
statically, but libraries exist and dlopen() calls succeed, why
do we care if it's statically linked?
Diffstat (limited to 'daemons/clvmd/lvm-functions.c')
| -rw-r--r-- | daemons/clvmd/lvm-functions.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/daemons/clvmd/lvm-functions.c b/daemons/clvmd/lvm-functions.c index 7250e04a..c74bf26f 100644 --- a/daemons/clvmd/lvm-functions.c +++ b/daemons/clvmd/lvm-functions.c @@ -724,7 +724,7 @@ void lvm_do_backup(const char *vgname) /* Called to initialise the LVM context of the daemon */ int init_lvm(int using_gulm) { - if (!(cmd = create_toolcontext(0, 1))) { + if (!(cmd = create_toolcontext(1))) { log_error("Failed to allocate command context"); return 0; } |