Differences

This shows you the differences between two versions of the page.

--- navhome [2007/10/01 09:59] – Removed unnecessary repetition of what is already documented at the target link. morten
+++ navhome [2008/06/02 09:46] (current) – morten
@@ Line 1: / Line 1: @@
 ====== The Home page components ======
@@ Line 14: / Line 5: @@
 ===== The main view =====
-{{screenshot:frontpage.png?600|}}
+{{screenshot:3.3:frontpage.png?600|}}
 The home page of NAV consists of the following elements;
@@ Line 24: / Line 15: @@
   - A NAV link box. \\  Edit the file ''webfront/nav-links.conf''. If the config file is empty or missing the box will not show up.
   - An external link box. \\  Edit the file ''webfront/external-links.txt''. If the config file is empty or missing the box will not show up.
-  - Contact information. \\ Edit the file ''webfront\contact-information.txt''. Relevant information is typically email and phone number to network and/or system operations.
+  - Contact information. \\ Edit the file ''webfront/contact-information.txt''. Relevant information is typically email and phone number to network and/or system operations.
 ===== The NAV bar =====
 The NAV bar is always available, not only on the home page, as a navigating bar on the top.  It provides buttons for login / logout, link to the toolbox, user-defined quicklinks, userinfo, and preferences.
 ==== Login / logout ====
@@ Line 47: / Line 27: @@
 controls which tools he or she may access.
-The user will be automatically logged out from NAV after a configurable time of inactivity. Adjust this parameter by altering the ''timeout'' value in ''webfront/webfront.conf''. The default value is FIXME 24 hours???
+The user will be automatically logged out from NAV after a configurable time of inactivity. Adjust this parameter by altering the ''timeout'' value in ''webfront/webfront.conf''. The default value is 1 hour (3600 seconds).
 === Use LDAP authentication ===
@@ Line 53: / Line 33: @@
 If you will have many NAV users and your organization's user database is available through LDAP, you should consider enabling LDAP authentication for the NAV web interface.
 LDAP configuration and usage [[ldapauthentication|is documented here]]
 ==== The tool box ====
-The toolbox lists all the NAV tools with a brief explaination and lets you navigate to your tool of interest.
+The toolbox lists all the NAV tools with a brief explanation and lets you navigate to your tool of interest. \\ The buildup of the tool box is based upon ''*.tool''-files in the ''/usr/share/nav/tools'' directory. Each tool file points to an icon, has a name, url, textual description and priority. The priority is basis for the order the various tools are presented in the toolbox.
@@ Line 99: / Line 80: @@
 ====== Log files ======
-''webfront.log'' gives information on failed logins and other issues. This log file is not there per default, Morten knows what to do FIXME
+NAV's web interface logs to the file ''webfront.log''.   This file doesn't exist by default.  It must be created in NAV's log directory and the user that the Apache server is running as must have write privileges to this file.  NAV uses the Python logging framework when logging to this file. You can create the config file ''logging.conf'' to define which log levels should be used for individual loggers.  If you wish to se debug messages for all parts of NAV from the web interface, create a ''logging.conf'' file containing the following:
+<code>
+[levels]
+root = DEBUG
+</code>
+If you only wish to se debug message for specifically web related modules, use this:
+<code>
+[levels]
+nav.web = DEBUG
+</code>