From 3bbdae633f4a1dda5f95ee6c61f18a1c8ef12250 Mon Sep 17 00:00:00 2001
From: Karel Zak
Date: Mon, 9 Jun 2014 11:59:44 +0200
Subject: 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>
---
 disk-utils/Makemodule.am | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'disk-utils/Makemodule.am')

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
 
-- 
cgit v1.2.3-55-g7522