summaryrefslogtreecommitdiffstats
path: root/disk-utils/Makemodule.am
diff options
context:
space:
mode:
authorKarel Zak2014-06-09 11:59:44 +0200
committerKarel Zak2014-06-09 11:59:44 +0200
commit3bbdae633f4a1dda5f95ee6c61f18a1c8ef12250 (patch)
tree2047e86cd087dbe1ff9d3c7d7eda348577dcfc2f /disk-utils/Makemodule.am
parentlib/fileutils: add stripoff_last_component() from libmount (diff)
downloadkernel-qcow2-util-linux-3bbdae633f4a1dda5f95ee6c61f18a1c8ef12250.tar.gz
kernel-qcow2-util-linux-3bbdae633f4a1dda5f95ee6c61f18a1c8ef12250.tar.xz
kernel-qcow2-util-linux-3bbdae633f4a1dda5f95ee6c61f18a1c8ef12250.zip
fsck: use private lock file rather than whole-disk directly
It seems overkill to lock directly whole-disk device (for -l) when we use the lock only to synchronize fsck instances. It's fsck private business, so don't use system files, but let's use private /run/fsck/<diskname>.lock file. Addresses: https://bugs.freedesktop.org/show_bug.cgi?id=79576 Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'disk-utils/Makemodule.am')
-rw-r--r--disk-utils/Makemodule.am2
1 files changed, 1 insertions, 1 deletions
diff --git a/disk-utils/Makemodule.am b/disk-utils/Makemodule.am
index 302aa6849..fb3b564cd 100644
--- a/disk-utils/Makemodule.am
+++ b/disk-utils/Makemodule.am
@@ -81,7 +81,7 @@ if BUILD_FSCK
sbin_PROGRAMS += fsck
dist_man_MANS += disk-utils/fsck.8
fsck_SOURCES = disk-utils/fsck.c
-fsck_LDADD = $(LDADD) libmount.la libblkid.la
+fsck_LDADD = $(LDADD) libmount.la libblkid.la libcommon.la
fsck_CFLAGS = $(AM_CFLAGS) -I$(ul_libmount_incdir) -I$(ul_libblkid_incdir)
endif