f757b4ebda
Comments in the shipped AppArmor profile state that fwknopd is assumed to be built with 'localstatedir=/var', which is misleading for several reasons: * AppArmor profile assumes that fwknopd's pidfile and digest cache are under /run/fwknop by the looks of it, i.e. 'localstatedir' is '/run'. * By default these files are placed under /var/run/fwknop. Thus this profile implicitly relies on the existence of '/var/run -> /run' symlink and won't work otherwise when 'localstatedir' is '/var' Since GitHub PR#152 was merged, 'localstatedir' can be simply set to '/run' for AppArmor users to avoid this confusion. This changeset does it. If anyone had it working before, they should have it working now as the shipped AppArmor profile required /run existence before as well.
14 lines
420 B
Bash
Executable File
14 lines
420 B
Bash
Executable File
#!/bin/sh -x
|
|
|
|
#
|
|
# This is a convenience script to run ./configure with the command line args
|
|
# that the AppArmor policy expects (sets up binary locations, sysconfdir,
|
|
# etc.). Execute this script from the top level fwknop sources directory.
|
|
#
|
|
|
|
if [ -x ./configure ]; then
|
|
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/run $@
|
|
else
|
|
echo "[*] Execute from the fwknop top level sources directory"
|
|
fi
|