http://bugzilla.novell.com/show_bug.cgi?id=510776 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |gs@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=510776 User alpha096@virginbroadband.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=510776#c2 Scott Couston changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |alpha096@virginbroadband.co | |m.au Info Provider|alpha096@virginbroadband.co | |m.au | --- Comment #2 from Scott Couston 2009-07-01 15:46:54 MDT --- The First page of help text is quote Auditd Log File Configuration The audit daemon logs all relevant audit events to the default log file /var/log/audit/audit.log. Events may come from the apparmor kernel module, from applications which use libaudit (e.g. PAM) or incidents caused by rules (e.g. file watches). More information about rules and the possiblity to add rules offers the dialog Rules for auditctl. Detailed information about the log file settings can be obtained from 'man auditd.conf'. Log File: Enter the full path name to the log file (or use Select File.) Format: set RAW to log all data or NOLOG to discard all audit information (does not affect data sent to the dispatcher). Flush: describes how to write the data to disk. If set to INCREMANTAL the Frequency parameter tells how many records to write before issuing an explicit flush to disk. Configure the maximum log file size and the action to take when this value is reached in Size and Action frame. If action is set to ROTATE the Number of Log Files specifies the number of files to keep. Computer Name Format describes how to write the computer name to the log file. If User is set the User Defined Name is used. Unquote 1.There needs to be a Hyperlink to man auditd.conf and or its location within the directory structure. 2. The messages that come from Apparmour are more easily dealt with in Apparmour reporting via proxmail to an email address in HTML.(Bad Example) 3. The words 'full pathway' should read 'absolute path' to be consistent. 4. The word 'possiblity' is spelt incorrectly 5. The description of FORMAT options is unclear, are you refering to raw text, and NOLOG seems to indicate the removal of all information? 6.All Flush options are not described 7.'Size and Action frame' all options are not disused 8. The Computer Name option 'FQD' is not discussed. If I continue with the other tabs things get far far worse. Writing help is always had as you have to write to the lowest possible denominator of experience of the person who is going to use the Module given its function. I am not suggesting this help text should be baby food, I would grab a non Linux, say a normal good user out of the building of yours to test the understanding and focus of the help text given the application nature. I never log a bug for the sake of missing 'x' I only wish what we all wish, a product that everyone can use and understand and moving outside of both our environments to be that person is often difficult and not an easy task. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.