diff --git a/pam-1.2.1-faillock.patch b/pam-1.2.1-faillock.patch
index b91a255..7a4209c 100644
--- a/pam-1.2.1-faillock.patch
+++ b/pam-1.2.1-faillock.patch
@@ -1290,9 +1290,9 @@ diff -up Linux-PAM-1.2.1/modules/pam_faillock/pam_faillock.c.faillock Linux-PAM-
+#endif /* #ifdef PAM_STATIC */
+
diff -up Linux-PAM-1.2.1/modules/pam_faillock/pam_faillock.8.xml.faillock Linux-PAM-1.2.1/modules/pam_faillock/pam_faillock.8.xml
---- Linux-PAM-1.2.1/modules/pam_faillock/pam_faillock.8.xml.faillock 2015-06-25 10:42:21.483374875 +0200
-+++ Linux-PAM-1.2.1/modules/pam_faillock/pam_faillock.8.xml 2015-10-16 14:04:45.810864576 +0200
-@@ -0,0 +1,396 @@
+--- Linux-PAM-1.2.1/modules/pam_faillock/pam_faillock.8.xml.faillock 2016-04-04 16:37:38.696260359 +0200
++++ Linux-PAM-1.2.1/modules/pam_faillock/pam_faillock.8.xml 2016-04-28 17:09:04.679596165 +0200
+@@ -0,0 +1,408 @@
+
+
@@ -1500,6 +1500,18 @@ diff -up Linux-PAM-1.2.1/modules/pam_faillock/pam_faillock.8.xml.faillock Linux-
+ entries by the faillock8 command.
+ The default is 600 (10 minutes).
+
++
++ Note that the default directory that pam_faillock
++ uses is usually cleared on system boot so the access will be also reenabled
++ after system reboot. If that is undesirable a different tally directory
++ must be set with the option.
++
++
++ Also note that it is usually undesirable to permanently lock
++ out the users as they can become easily a target of denial of service
++ attack unless the usernames are random and kept secret to potential
++ attackers.
++
+
+
+