yast-audit-laf/master — Afrikaans @ openSUSE Weblate: &Load

Zen

	English	Afrikaans	Actions
	Value and Action for Space Is Running Low
	&Admin Space Left (MB)
	Ac&tion	Aksie
	Action Mail Account	Vscan-rekening
	Action on Error or Disk Full
	Disk &Full Action	Skyfaktivering
	Disk &Error Action	Skyfaktivering
	&Set Enabled Flag	Kliënt ontsper
	Auditing enabled	Opgawemaak ontsper
	Auditing disabled	Opgawemaak versper
	Rules are locked (until next boot)
	Edit the rules for the audit subsystem here:
	&Check Syntax	Basiese sintaks:
	&Restore 'audit.rules'	Teruggesteldelêers:
	R&estore and Reset	Terugstelopsies
	&Load	&Laai
	<p><b><big>Initializing Configuration of Linux Audit Framework</big></b><br> </p>	<p><b><big>Inisialiseer Konfigurasie</big></b><br> Wag asseblief...<br></p>
	<p><b><big>Aborting Initialization:</big></b><br> Safely abort the configuration utility by pressing <b>Abort</b> now.</p>	<p><b><big>Staak inisialisering:</big></b><br> Staak die konfigurasienutsprogram veilig deur <b>Staak</b> nou te druk.</p>
	<p><b><big>Saving auditd Configuration and Rules</big></b><br> </p>	<p><b><big>Berg van xinetd-konfigurasie</big></b><br> Wag, asseblief ...<br></p>
	<p><b><big>Aborting Saving:</big></b><br> Abort the save procedure by pressing <b>Abort</b>. An additional dialog informs whether it is safe to do so. </p>	<p><b><big>Staak berging:</big></b><br> Staak die bergingsprosedure deur <b>Staak</b> te druk. 'n Bykomende dialoog deel mee of dit veilig is om dit te doen. </p>
	<p><b><big>Auditd Log File Configuration</big></b><br> The audit daemon is the component of the Linux Auditing System which is responsible for writing all relevant audit events to the log file <i>/var/log/audit/audit.log</i> (default). Events may come from the <i>apparmor</i> kernel module, from applications which use <i>libaudit</i> (e.g. PAM) or incidents caused by rules (e.g. file watches).</p>
	<p>The <b>Rules for auditctl</b> dialog offers more information about rules and the possibility to add rules. Detailed information about the log file settings can be obtained from the manual page ('man auditd.conf').</p>	<p><b><big>Voeg 'n nuwe gedeelde by</big></b><br> Voer hier die basiese inligting oor 'n gedeelde wat bygevoeg moet word, by.</p>
	<p><b>Log File</b>: Enter the full path name to the log file (or use <b>Select File</b>.)</p>
	<p><b>Format</b>: set <i>RAW</i> to log all data (store in a format exactly as the kernel sends it) or <i>NOLOG</i> to discard all audit information instead of writing it on disk (does not affect data sent to the dispatcher).</p>
	<p><b>Flush</b>: describes how to write the data to disk. If set to <i>INCREMENTAL</i> the <b>Frequency</b> parameter tells how many records to write before issuing an explicit flush to disk. <i>NONE</i> means: no special effort is made to flush data, <i>DATA</i>: keep data portion synced, <i>SYNC</i>: keep data and meta-data fully synced.</p>
	<p>Configure the maximum log file size (in megabytes) and the action to take when this value is reached via <b>Size and Action</b>.</p>
	<p>If the action is set to <i>ROTATE</i> the <b>Number of Log Files</b> specifies the number of files to keep. Set to <i>SYSLOG</i>, the audit daemon will write a warning to /var/log/messages. With <i>SUSPEND</i> the daemon stops writing records to disk. <i>IGNORE</i> means do nothing, <i>KEEP_LOGS</i> is similar to ROTATE, but log files are not overwritten.</p>
	<p><b>Computer Name Format</b> describes how to write the computer name to the log file. If <i>USER</i> is set, the <b>User Defined Name</b> is used. <i>NONE</i> means no computer name is inserted. <i>HOSTNAME</i> uses the name returned by the 'gethostname' syscall. <i>FQD</i> uses the fully qualified domain name.</p>
	<p><b><big>Auditd Dispatcher Configuration</big></b><br> Detailed information about the dispatcher settings can be obtained from the manual page ('man auditd.conf').</p>	<p><b><big>Voeg 'n nuwe gedeelde by</big></b><br> Voer hier die basiese inligting oor 'n gedeelde wat bygevoeg moet word, by.</p>
	<p><b>Dispatcher</b>: The dispatcher program is started by the audit daemon and gets all audit events on stdin.</p>
	<p><b>Communication</b>: Controls the communication between the daemon and the dispatcher program. A <i>lossy</i> communication means that events going to the dispatcher are discarded when the queue (a 128kB buffer) is full. Choose <i>lossless</i> if you want a blocking/lossless communication.</p>