Novell IFOLDER 3 - ADMINISTRATION, Руководство пользователя

Страница: 69 / 148

Managing an iFolder Enterprise Server 69
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
In the Log4net terminology, each output destination is defined in an XML
appender
tag. If you do
not want to log events for the Simias Service or for file access, comment out (
!--
) the related
appender
tag and its child elements for that log file.
7.5 Backing Up the iFolder Server
1 Stop the iFolder server by entering the following command as root user:
/etc/init.d/apache2 stop
2 Use your normal file system backup procedures to back up the following data:
• Simias store directory
The default location is
/var/opt/novell/ifolder3/simias
.
• Simias configuration file
The default locations are
/var/lib/wwwrun/.local/share/simias/
Simias.config or /home/wwwrun/.local/share/simias/
Simias.config
.
3
Start the iFolder server by entering the following command as root user:
Level of Simias Services
messages
<level
value=”
status ” />
(Use only for the
Simias.log
.)
The type of messages or level of
detail you want to capture for the
log. Valid levels include the
following:
OFF
FATAL
ERROR
WARN
INFO
DEBUG
ALL
<level value="ERROR" />
Fields to report for file access
events
<header
value=”
layout ” />
(Use only for the
Simias.access.log
.)
Specify which fields to report and
the order you want them to appear
for each entry. Valid fields include
the following:
date
time
method
(program call or event)
status
(success or failure)
user
uri
(relative path of the file in an
iFolder)
id
(node key)
The fields are tab delimited (
\t
) by
default, but you can specify a
space or tab character in front of
the field name to serve as a
delimiter.
<header value="#version:
1.0&#xD;&#xA;#Fields:\td
ate\ttime\tmethod\tstatu
s\tuser\turi\tid\t&#xD;&
#xA;" />
Parameters Description Examples