mirror of
https://github.com/Zeckmathederg/glfs.git
synced 2025-02-03 14:47:17 +08:00
edits caught by Bill
git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1058 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
parent
30f1425fd9
commit
b2a7072d47
@ -31,8 +31,9 @@ other password required pam_unix.so nullok
|
|||||||
|
|
||||||
# End /etc/pam.conf</screen>
|
# End /etc/pam.conf</screen>
|
||||||
|
|
||||||
<para>The <application><acronym>pam</acronym></application> man page provides a
|
<para>The <application><acronym>PAM</acronym></application> man page,
|
||||||
good starting point for descriptions of fields and allowable entries. The
|
<command>man pam</command> provides a good starting point for descriptions of
|
||||||
|
fields and allowable entries. The
|
||||||
<ulink url="http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam.html">
|
<ulink url="http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam.html">
|
||||||
Linux-PAM guide for system administrators</ulink> and two
|
Linux-PAM guide for system administrators</ulink> and two
|
||||||
<application><acronym>PAM</acronym></application> hints located at
|
<application><acronym>PAM</acronym></application> hints located at
|
||||||
|
@ -28,7 +28,7 @@ Custom policy file for SuSE 7.2 system</screen>
|
|||||||
Get ideas from the examples above and read <filename>
|
Get ideas from the examples above and read <filename>
|
||||||
/usr/share/doc/tripwire/policyguide.txt</filename>. <filename>twpol.txt
|
/usr/share/doc/tripwire/policyguide.txt</filename>. <filename>twpol.txt
|
||||||
</filename> is a good policy file for beginners as it will note any changes to
|
</filename> is a good policy file for beginners as it will note any changes to
|
||||||
the filesystem and can even be used as an annoying way of keeping track of
|
the filesystem and can even be used as an annoying way of keeping track of
|
||||||
changes for uninstallation of software.</para>
|
changes for uninstallation of software.</para>
|
||||||
|
|
||||||
<para>After your policy file has been transferred to <filename>/etc/tripwire/
|
<para>After your policy file has been transferred to <filename>/etc/tripwire/
|
||||||
@ -44,13 +44,14 @@ tripwire -m i</command></userinput></screen>
|
|||||||
</sect3>
|
</sect3>
|
||||||
|
|
||||||
<sect3><title>Usage Information</title>
|
<sect3><title>Usage Information</title>
|
||||||
<para>To use tripwire after this and run a report using the following command:
|
<para>To use tripwire after this and run a report, use the following command:
|
||||||
|
|
||||||
<screen><userinput><command>tripwire -m c > /etc/tripwire/report.txt
|
<screen><userinput><command>tripwire -m c > /etc/tripwire/report.txt
|
||||||
</command></userinput></screen></para>
|
</command></userinput></screen></para>
|
||||||
|
|
||||||
<para>View the output to check the integrity of your files. An automatic
|
<para>View the output to check the integrity of your files. An automatic
|
||||||
integrity report can be produced by using fcron. </para>
|
integrity report can be produced by using a cron facility to schedule
|
||||||
|
the runs. </para>
|
||||||
|
|
||||||
<para>Please note that after you run an integrity check, you must check
|
<para>Please note that after you run an integrity check, you must check
|
||||||
the report or email and then modify the tripwire database of the files
|
the report or email and then modify the tripwire database of the files
|
||||||
|
Loading…
Reference in New Issue
Block a user