The ServiceName uniquely identifies an APPX Audit Log Service. When creating (installing) an Audit Log Service, the SERVICENAME value may be any string value that conforms to the rules for valid filenames on your server. If this option is omitted when an Audit Log Service is being created, the Audit Log Service will be created with a default ServiceName based on the following template: "appxd-" followed by the specified TCP/IP port number, e.g "appxd-8060".

The LogRotationInterval identifies the maximum time in seconds that an Audit Log file should be used before being closed and a new audit log file is created. The default value of 86400 is the number of seconds in one day so, by default, the Audit Log Service will create a new audit log file each day

The LogRotationSize is the maximum size that an Audit Log file is allowed to be. When an audit log file reaches the specified MAXSIZE, it will be closed and a new audit log file will be created.

/tmp/appx-11-Jun-08

cd /usr/local/appx/services
chown root appxAuditMgr
chgrp appxgrp appxAuditMgr
chmod 4775 appxAuditMgr

1. A configuration file (ini) is created
2. An environment file (env) is created
3. A service is created, including required init files and links. ( On Red Hat, /etc/init.d/ )

Method 2 - Text Editor

[root@500test services]# ./appxAuditMgr -status appxLog8070 
up and running (process 2390 servicing port 8070)

[root@500test services]# service appxLog8070 status 
up and running (process 2390 servicing port 8070)

The appxAuditMgr service configuration commands are used to create, configure, and remove an instance of an APPX Audit Log Service.

The -install command is used to configure a new instance of an APPX Audit Log Service. Either form of the install command may be used.

The -replace command is used to replace an existing Audit Log Service with a new Audit Log Service with the same name. The -replace command is effectively the same as a -remove command followed by an -install command. After updating the configuration files, the -replace command restarts the service. Note that when specifying variables on the command line, you must prefix them with a dash if you are referring to settings such as DisplayName, or without a dash if you are referring to environment variables.

The -remove command is used to remove an existing Audit Log Service. The -remove command will remove the configuration files (ini and env) and the corresponding operating system service. If the service is running when the -remove command is executed, the -remove command will first stop the service and then remove the service.

The ServiceName uniquely identifies an APPX Audit Log Service. When creating (installing) an Audit Log Service, the SERVICENAME value may be any string value that conforms to the rules for valid filenames on your server. If this option is omitted when an Audit Log Service is being created, the Audit Log Service will be created with a default ServiceName based on the following template: "appxd-" followed by the specified TCP/IP port number, e.g "appxd-8060".

When the service is started, two log files are created in the LOGDIR directory - an Audit Log Service log file (.log) and a status file (.stat). Both log files have the same name as the ServiceName but one has a file extension of .log and the other has a file extension of .stat. If the LogDirectory option is not specified, the log files are created in the /tmp directory.

The only valid value when configuring an Audit Log Service is "logmonitor". Note: This option must be specified.

This option can be used to temporarily disable or "turn off" the Audit Log Service. If set to true, the Audit Log Service will still run but it will not accept requests to log data from APPX sessions.

Used with -install option to specify the type of operating system that the service script is to be created for. If this option is not specified, appxAuditMgr will determine which type of service script to install.

The LogRotationInterval identifies the maximum time in seconds that an Audit Log file should be used before being closed and a new audit log file is created. The default value of 86400 is the number of seconds in one day so, by default, the Audit Log Service will create a new audit log file each day

The LogRotationSize is the maximum size that an Audit Log file is allowed to be. When an audit log file reaches the specified MAXSIZE, it will be closed and a new audit log file will be created.

Configure the service to listen for audit log requests on the specified TCP/IP PORT number. This option is required with the -install option. You may choose any TCP/IP PORT number that is not reserved or already being used on your system.

VARIABLE=VALUE

You can include a space-separated list of environment variables at the end of the command line when you use the -install option. These environment variables will be saved in the env file that is created. There is currently no reason to use this feature.

appxAuditMgr [-start | -stop | -restart | -status] {SERVICENAME | -serviceName=SERVICENAME}

-start | < blank >

Start an instance of the Audit Log Service using the configuration information in the SERVICENAME.ini and the SERVICENAME.env files.

Stop the instance of the Audit Log Service that was started with the SERVICENAME.ini file.

Restart (stop and then start) the instance of the Audit Log Service that was started with the SERVICENAME.ini file.

Report the status of the instance of the Audit Log Service that was started with the SERVICENAME.ini file.

[root@localhost services]# ./appxAuditMgr -install -name=appxLog8070 -port=8070 -ServiceType=logmonitor
Configuration written to:  appxLog8070.ini
Environment written to:    appxLog8070.env
Service script written to: /etc/init.d/appxLog8070
Configuration complete
Registering service
Starting appxLog8070: serviceName: appxLog8070
servicePath: /usr/local/appx500/services/
Looking for config file in appxLog8070.ini
Writing process ID to /var/run/appxLog8070.pid
running as process 12859 servicing port 8070
up and running (process 12859 servicing port 8070)
Installation Complete

The Configuration File (ini)

# Appx connection manager configuration file
#
#  You can change this file by hand, or
#  use the uappxd program for better results
#
#  blank lines are ignored
#
#  anything following a '#' is treated as a comment
#
#  case is not important on the left-hand side
#  properties whose descriptions end in a '?' are
#  boolean and should be set to true or false
# --------------------------------------------------
# AppxApplication           =                    #startup application for spawned engines
# AppxDatabase              =                    #startup database for spawned engines
AppxExecutable              = /usr/local/appx500/appx#pathname to Appx engine
# AppxProcessName           =                    #startup process name for spawned engines
# AppxProcessType           =                    #startup process type for spawned engines
# AuthenticationMethod      = OS-User            #authentication method (OS-User, Appx-User, HT-User(filename))
DisplayName                 = appxLog8070        #descriptive name
# ImpersonateGID            = true               #change effective grouo ID for spawned engines?
# ImpersonateGroup          = User               #[LogonUser, NamedGroup(groupname), ServiceOwner]
# ImpersonateUID            = true               #change effective user ID for spawned engines?
# ImpersonateUser           = LogonUser          #[LogonUser, NamedUser(username), ServiceOwner]
# LoadSystemEnvironment     = true               #load default system-defined environment variables into spawned engines?
# LogDirectory              = /tmp               #directory where log file should reside
# LogNamePattern            = /tmp/appxlog%N.xml #audit log filename pattern (see man strftime for details
# LogRotationInterval       = 86400              #number of seconds between audit log rotations
# LogRotationSize           = 1G                 #maximum audit log file size
# RequireSSL                = false              #Require SSL-secured connections?
# RequireSSLClientCertificates = false              #require SSL-client certificates?
# ServerCertificateFile     =                    #pathname of server's X509 certificate (leave blank for anonymous connections
# ServerPrivateKeyFile      =                    #pathname of server's private key file (unlocks the ServerCertificateFile)
# ServerPrivateKeyPassphrase =                    #passphrase that unlocks ServerPrivateKeyFile
# ServiceDisable            = false              #disable this service?
# ServiceDisableAppxKeys    = false              #disable keyboard mapping?
# ServiceDisableFMS         = false              #disable AppxNET connections?
# ServiceDisableLogins      = false              #disable interactive logins?
# ServiceEnableCmds         = true               #allow client-side startup options?
ServiceName                 = appxLog8070        #name of service
ServiceType                 = logmonitor         #service type (login or logmonitor)
SockPort                    = 8070               #port number to service
# SSLMode                   = Optional           #SSL connection type (optional, required, disabled)
# TCPEnableKeepAlive        = true               #Enable TCP dead-connection detection
# TCPKeepCount              = 8                  #Maximum number of keep-alive pings
# TCPKeepIdle               = 300                #Idle time before ping sent to client (in seconds)
# TCPKeepInterval           = 60                 #Interval between keep-alive pings
# TCPNoDelay                = true               #disable TCP packet filling delay?
# TrustedCAFile             =                    #determines which client certificates to trust
# Umask                     =                    #umask (file creation mask) given to spawned engines

The Environment File (env)

# Appx connection manager environment variables

The Status File (stat)

appxLog8070 running as process 8665

*Daemonize = true

Red Hat service command.

Usage (service)

Synopsis - service Command

service [serviceName] [start|stop|restart|status]

Examples:

Warnings:

Enhancement Suggestions

LogNamePattern = /tmp/appxlog%N.xml

/tmp/appx-11-Jun-08

kill -s SIGUSR1 <PID>

where PID is a process ID of the audit log listener. Existent log will be closed and rotated to the next one.

Microsoft XML Notepad

Web Browser

xslt

NOTES:

If log file is not closed/rotated properly, Internet Explorer will display your .xml file, but it will show an error at the end of the file saying "File not closed". Firefox, however, will throw an error and won't display file at all

In Linux, the way to close log and rotate it is to issue kill -s SIGUSR1 PID command.

How to close and rotate the log in Windows?

APPX Audit Log Feature 

This page describes the APPX Audit Log feature and provides instructions for enabling the APPX Audit Log feature.

Installing the APPX Audit Log Manager Command ( appxAuditMgr)

cd /usr/local/appx/services

ls -l appxAuditMgr

-rwsrwxr-x 1 root appxgrp    636843 Jul 11 07:31 appxAuditMgr

Creating and Configuring an Audit Log Service

Service Name 

Managing an Audit Log Service

[root@500test services]# ./appxAuditMgr -status appxLog8070 
up and running (process 2390 servicing port 8070)

Method 2 - O/S Services 

[root@500test services]# service appxLog8070 status 
up and running (process 2390 servicing port 8070)

The ServiceName uniquely identifies an APPX Audit Log Service. When creating (installing) an Audit Log Service, the SERVICENAME value may be any string value that conforms to the rules for valid filenames on your server. If this option is omitted when an Audit Log Service is being created, the Audit Log Service will be created with a default ServiceName based on the following template: "appxd-" followed by the specified TCP/IP port number, e.g "appxd-8060".

The only valid value when configuring an Audit Log Service is "logmonitor". Note: This option must be specified.

This option can be used to temporarily disable or "turn off" the Audit Log Service. If set to true, the Audit Log Service will still run but it will not accept requests to log data from APPX sessions.

The LogRotationInterval identifies the maximum time in seconds that an Audit Log file should be used before being closed and a new audit log file is created.  The default value of 86400 is the number of seconds in one day so, by default, the Audit Log Service will create a new audit log file each day

The LogRotationSize is the maximum size that an Audit Log file is allowed to be.  When an audit log file reaches the specified MAXSIZE, it will be closed and a new audit log file will be created.

Configure the service to listen for audit log requests on the specified TCP/IP PORT number. This option is required with the -install option. You may choose any TCP/IP PORT number that is not reserved or already being used on your system.

VARIABLE=VALUE

You can include a space-separated list of environment variables at the end of the command line when you use the -install option. These environment variables will be saved in the env file that is created.  There is currently no reason to use this feature.

-start | < blank >

Start an instance of the Audit Log Service using the configuration information in the SERVICENAME.ini and the SERVICENAME.env files.

Stop the instance of the Audit Log Service that was started with the SERVICENAME.ini file.

Restart (stop and then start) the instance of the Audit Log Service that was started with the SERVICENAME.ini file.

Report the status of the instance of the Audit Log Service that was started with the SERVICENAME.ini file.

[root@localhost services]# ./appxAuditMgr -install -name=appxLog8070 -port=8070 -ServiceType=logmonitor

# Appx connection manager configuration file

# AppxApplication            =                     #startup application for spawned engines # AppxDatabase               =                     #startup database for spawned engines AppxExecutable               = /usr/local/appx500/appx#pathname to Appx engine # AppxProcessName            =                     #startup process name for spawned engines # AppxProcessType            =                     #startup process type for spawned engines # AuthenticationMethod       = OS-User             #authentication method (OS-User, Appx-User, HT-User(filename)) DisplayName                  = appxLog8070         #descriptive name # ImpersonateGID             = true                #change effective grouo ID for spawned engines? # ImpersonateGroup           = User                #[LogonUser, NamedGroup(groupname), ServiceOwner] # ImpersonateUID             = true                #change effective user ID for spawned engines? # ImpersonateUser            = LogonUser           #[LogonUser, NamedUser(username), ServiceOwner] # LoadSystemEnvironment      = true                #load default system-defined environment variables into spawned engines? # LogDirectory               = /tmp                #directory where log file should reside # LogNamePattern             = /tmp/appxlog%N.xml  #audit log filename pattern (see man strftime for details # LogRotationInterval        = 86400               #number of seconds between audit log rotations # LogRotationSize            = 1G                  #maximum audit log file size # RequireSSL                 = false               #Require SSL-secured connections? # RequireSSLClientCertificates = false               #require SSL-client certificates? # ServerCertificateFile      =                     #pathname of server's X509 certificate (leave blank for anonymous connections # ServerPrivateKeyFile       =                     #pathname of server's private key file (unlocks the ServerCertificateFile) # ServerPrivateKeyPassphrase =                     #passphrase that unlocks ServerPrivateKeyFile # ServiceDisable             = false               #disable this service? # ServiceDisableAppxKeys     = false               #disable keyboard mapping? # ServiceDisableFMS          = false               #disable AppxNET connections? # ServiceDisableLogins       = false               #disable interactive logins? # ServiceEnableCmds          = true                #allow client-side startup options? ServiceName                  = appxLog8070         #name of service ServiceType                  = logmonitor          #service type (login or logmonitor) SockPort                     = 8070                #port number to service # SSLMode                    = Optional            #SSL connection type (optional, required, disabled) # TCPEnableKeepAlive         = true                #Enable TCP dead-connection detection # TCPKeepCount               = 8                   #Maximum number of keep-alive pings # TCPKeepIdle                = 300                 #Idle time before ping sent to client (in seconds) # TCPKeepInterval            = 60                  #Interval between keep-alive pings # TCPNoDelay                 = true                #disable TCP packet filling delay? # TrustedCAFile              =                     #determines which client certificates to trust # Umask                      =                     #umask (file creation mask) given to spawned engines

# Appx connection manager environment variables

appxLog8070 running as process 8665

*Daemonize = true

1. When executing the appxAuditMgr command with the -install option, you must include the -name option.
2. When executing the the appxAuditMgr command with the -install option, you must include the - DisplayName option.  If you do not, the ps command will not display a meaningful name for the running service.

Using a Pattern in a Log File Name

%a The abbreviated weekday name according to the current locale.

The LogRotationInterval identifies the maximum time in seconds that an Audit Log file should be used before being closed and a new audit log file is created.  The default value of 86000 is the number of seconds in one day so, by default, the Audit Log Service will create a new audit log file each day

APPX Audit Log Feature 

Installing the APPX Audit Log Manager Command ( appxAuditMgr)

Creating and Configuring an Audit Log Service

Service Name 

Managing an Audit Log Service

[root@500test services]# appxLogMgr -status appxLog8070

Method 2 - O/S Services 

[root@500test services]# service appxLog8070 status

The appxAuditMgr service configuration commands are used to create, configure, and remove an instance of an APPX Audit Log Service.

The -install command is used to configure a new instance of an APPX Audit Log Service. Either form of the install command may be used.

The -replace command is used to replace an existing Audit Log Service with a new Audit Log Service with the same name. The -replace command is effectively the same as a -remove command followed by an -install command. After updating the configuration files, the -replace command restarts the service. Note that when specifying variables on the command line, you must prefix them with a dash if you are referring to settings such as DisplayName, or without a dash if you are referring to environment variables.

The -remove command is used to remove an existing Audit Log Service. The -remove command will remove the configuration files (ini and env) and the corresponding operating system service. If the service is running when the -remove command is executed, the -remove command will first stop the service and then remove the service.

The ServiceName uniquely identifies an APPX Audit Log Service. When creating (installing) an Audit Log Service, the SERVICENAME value may be any string value that conforms to the rules for valid filenames on your server. If this option is omitted when an Audit Log Service is being created, the Audit Log Service will be created with a default ServiceName based on the following template: "appxd-" followed by the specified TCP/IP port number, e.g "appxd-8060".

When the service is started, two log files are created in the LOGDIR directory - an Audit Log Service log file (.log) and a status file (.stat). Both log files have the same name as the ServiceName but one has a file extension of .log and the other has a file extension of .stat. If the LogDirectory option is not specified, the log files are created in the /tmp directory.

The only valid value when configuring an Audit Log Service is "logmonitor". Note: This option must be specified.

This option can be used to temporarily disable or "turn off" the Audit Log Service. If set to true, the Audit Log Service will still run but it will not accept requests to log data from APPX sessions.

Used with -install option to specify the type of operating system that the service script is to be created for. If this option is not specified, appxAuditMgr will determine which type of service script to install.

The LogRotationInterval identifies the maximum time in seconds that an Audit Log file should be used before being closed and a new audit log file is created.  The default value of 86000 is the number of seconds in one day so, by default, the Audit Log Service will create a new audit log file each day

The LogRotationSize is the maximum size that an Audit Log file is allowed to be.  When an audit log file reaches the specified MAXSIZE, it will be closed and a new audit log file will be created.

Configure the service to listen for audit log requests on the specified TCP/IP PORT number. This option is required with the -install option. You may choose any TCP/IP PORT number that is not reserved or already being used on your system.

VARIABLE=VALUE

You can include a space-separated list of environment variables at the end of the command line when you use the -install option. These environment variables will be saved in the env file that is created.  There is currently no reason to use this feature.

appxAuditMgr [-start | -stop | -restart | -status] {SERVICENAME | -serviceName=SERVICENAME}

-start | < blank >

Start an instance of the Audit Log Service using the configuration information in the SERVICENAME.ini and the SERVICENAME.env files.

Stop the instance of the Audit Log Service that was started with the SERVICENAME.ini file.

Restart (stop and then start) the instance of the Audit Log Service that was started with the SERVICENAME.ini file.

Report the status of the instance of the Audit Log Service that was started with the SERVICENAME.ini file.

# AppxApplication            =                     #startup application for spawned engines # AppxDatabase               =                     #startup database for spawned engines AppxExecutable               = /usr/local/appx500/appx#pathname to Appx engine # AppxProcessName            =                     #startup process name for spawned engines # AppxProcessType            =                     #startup process type for spawned engines # AuthenticationMethod       = OS-User             #authentication method (OS-User, Appx-User, HT-User(filename)) DisplayName                  = appxLog8070         #descriptive name # ImpersonateGID             = true                #change effective grouo ID for spawned engines? # ImpersonateGroup           = User                #[LogonUser, NamedGroup(groupname), ServiceOwner] # ImpersonateUID             = true                #change effective user ID for spawned engines? # ImpersonateUser            = LogonUser           #[LogonUser, NamedUser(username), ServiceOwner] # LoadSystemEnvironment      = true                #load default system-defined environment variables into spawned engines? # LogDirectory               = /tmp                #directory where log file should reside # LogNamePattern             = /tmp/appxlog%N.xml  #audit log filename pattern (see man strftime for details # LogRotationInterval        = 86400               #number of seconds between audit log rotations # LogRotationSize            = 1G                  #maximum audit log file size # RequireSSL                 = false               #Require SSL-secured connections? # RequireSSLClientCertificates = false               #require SSL-client certificates? # ServerCertificateFile      =                     #pathname of server's X509 certificate (leave blank for anonymous connections # ServerPrivateKeyFile       =                     #pathname of server's private key file (unlocks the ServerCertificateFile) # ServerPrivateKeyPassphrase =                     #passphrase that unlocks ServerPrivateKeyFile # ServiceDisable             = false               #disable this service? # ServiceDisableAppxKeys     = false               #disable keyboard mapping? # ServiceDisableFMS          = false               #disable AppxNET connections? # ServiceDisableLogins       = false               #disable interactive logins? # ServiceEnableCmds          = true                #allow client-side startup options? ServiceName                  = appxLog8070         #name of service ServiceType                  = logmonitor          #service type (login or logmonitor) SockPort                     = 8070                #port number to service # SSLMode                    = Optional            #SSL connection type (optional, required, disabled) # TCPEnableKeepAlive         = true                #Enable TCP dead-connection detection # TCPKeepCount               = 8                   #Maximum number of keep-alive pings # TCPKeepIdle                = 300                 #Idle time before ping sent to client (in seconds) # TCPKeepInterval            = 60                  #Interval between keep-alive pings # TCPNoDelay                 = true                #disable TCP packet filling delay? # TrustedCAFile              =                     #determines which client certificates to trust # Umask                      =                     #umask (file creation mask) given to spawned engines

1. When executing the the appxAuditMgr command with the -install option, you must include the - DisplayName option.  If you do not, the ps command will not display a meaningful name for the running service.

<?XML:NAMESPACE PREFIX = V />@0 1 0">@1">@2 1 2">@3 21600 pixelWidth">@3 21600 pixelHeight">@0 0 1">servername:8064

Then click on Log File Parameters and make sure you check parameters that you wish to log:

Now you are ready to define a new FMS group for the monitor.

To add a new FMS group you need to go to System Administration, Configuration, File System Groups and press F9 to add a new one for the monitor.

Give it an FMS group of 1 and click on 'FMS group attributes' button. On that screen enter the name of your Log Profile in the 'Log Profile' field. Note that if you already have an FMS group that is used by the file(s) you wish to monitor, you can simply add the Log Profile name to the existing FMS group. If the FMS group refers to a RDBMS (such as Oracle, SQL Server, etc), then only changes made by Appx will be logged.

You can now assign this FMS group to the file(s) that you wish to monitor.

More About the xml Audit Log file

Using a Pattern in a Log File Name

Once you have created this new Service Type, it will create .ini and .env files for you. In our example, appxAuditMgr will create myLogMonitor.ini and myLogMonitor.env files in the ./services directory. You can change the name of the log file (which defaults to /tmp/appxlog%N.xml) by setting the LogNamePattern in the myLogMonitor.ini file. You can also change the LogRotationInterval and LogRotationSize.

Since we rotate audit logs, you specify a LogNamePattern instead of just a filename. The pattern can include %N (which is translated to a monotonically increasing counter: 0, 1, 2, ..) or any of the date/time format specs. supported by the strftime() function (see 'man strftime' for a list of the patterns). For example, a LogNamePattern of '/tmp/appx_%F.xml' would generate names like:

/tmp/appx_2007-01-31.xml

/tmp/appx_2007-02-28.xml

The default pattern (as reflected in the serviceName. ini file) is:

LogNamePattern = /tmp/appxlog%N.xml

Each time the log monitor rotates to a new log file, it replaces %N with the next number in sequence (it was always starting at 0). You can use other specifiers in the LogNamePattern too, for example, "/tmp/appx-%D-%B-%Y" would result in file names like:

/tmp/appx-11-Jun-08

/tmp/appx-12-Jun-08

...

If you restart the log monitor on 11-Jun-08 (and your LogNamePattern specifies %D-%B-%Y), any existing log file with that name would be replaced. Of course, you can include time components in the LogNamePattern to avoid that problem (or add %N to the pattern to include a sequence number). Here's the complete list of valid specifiers (from the strftime man page):

%a The abbreviated weekday name according to the current locale.

How to Rotate the Audit Log File

To close existent log file and rotate the log, you need issue the following command:

kill -s SIGUSR1 <PID>

where PID is a process ID of the audit log listener. Existent log will be closed and rotated to the next one.

How to View Audit Log Events

The log file is generated in XML format. Why XML, and not Appx/IO? The biggest reason is the size of the log files. On large, active systems the number of events can exceed the maximum file size.

You can view the log file with a browser, with XML Notepad, or you can download SQL Express (free) and write queries against your XML file. You can also use the various xlst processing programs to create queries (such as xsltproc or xalan from Apache).

Microsoft XML Notepad

Web Browser

xslt

Databases

XML files can easily be imported into a RDBMS, which does not have the same file size limitation.

Audit Log Events

Each Audit Log document contains one primary enclosing <events> node which contains one or more <event> nodes. Each <event> node contains an eventID node which has a <type> element that identifies the type of event that is being logged. A variety of additional nodes (shown in the table below) are included in each <event> node depending on the value of the <type> element. The following values may occur for the <type> element:

Sample scripts

Here are some sample xslt processing commands that you can use to do inquiries against the raw XML data.

The attached file 'structure.xslt' will extract any file create events from a log and produces an HTML table that shows the structure of each file that you create.

The attached file 'subrs.xslt' extracts all events where the process type is SUBR and produces an HTML summary table that shows the user id, date, time, event ID, application ID, version, and process name.

To use a stylesheet with xsltproc (the XSLT processor from libxml/xmlsoft):

$ xslt stylesheetFileName logFileName >output.html

for example:

$ xslt /stylesheets/structure.xslt /tmp/appxlog0.xml > /tmp/fileCreates.html

To use a stylesheet with xalan (the XSLT processor from Apache):

$ xalan -xsl stylesheetFileName <logFileName >output.html

for example:

$ xalan -xsl /stylesheets/structure.xslt < /tmp/appxlog0.xml > /tmp/fileCreates.html

Need examples of loading XML Data into an RDBMS

NOTES:

If log file is not closed/rotated properly, Internet Explorer will display your .xml file, but it will show an error at the end of the file saying "File not closed". Firefox, however, will throw an error and won't display file at all

In Linux, the way to close log and rotate it is to issue kill -s SIGUSR1 PID command.

How to close and rotate the log in Windows?

Comments:

Read what other users have said about this page or add your own comments.

<--/commentPlugin-->

-- SteveFrizzell - 20 Jun 2008

%a The abbreviated weekday name according to the current locale.

-- SteveFrizzell - 20 Jun 2008