Sun Java System Calendar Server 6.3 Administration Guide

ProcedureTo Configure Calendar Logging

  1. Log in as an administrator with permission to change the configuration.

  2. Change to the /etc/opt/SUNWics5/cal/config directory.

  3. Save your old ics.conf file by copying and renaming it.

  4. Edit one or more of the parameters shown in the following table:


    Description and Default Value  


    This log file contains history of the administrative tool commands issued. The default is "admin.log".


    Size in bytes for log buffers. The default is "0". Specify the size of each entry in the log files. If your buffers fill up too fast, consider making them larger.


    Name of the log file for logging Database Wire Protocol related administrative tools. The default is "dwp.log". Specify one per front-end server.


    Number of seconds before the log files expire. The default is "604800". After this time, a cleanup routine will purge the log. If you want to archive the log, you must write your own routine.


    Number of seconds between the flushing of buffers to log files. the default is "60".

    If your system experiences a high volume of log information and your buffers fill up before 60 seconds, you will lose information. In that case consider decreasing this time interval. Note that decreasing the time interval increases system overhead. 


    Name of the current log file for the cshttpd service. The default is "http.log".


    Name of the current HTTP access log file. 


    Directory location of the log files. The default is "/var/opt/SUNWics5/logs".


    Determines the level of detail the server will log. Each log entry is assigned one of these levels (starting with the most severe): CRITICAL, ALERT, ERROR, WARNING, NOTICE, INFORMATION, and DEBUG. The default is “NOTICE”.

    If you set to CRITICAL, Calendar Server logs the least amount of detail. If you want the server to log the most amount of detail, specify DEBUG.

    Each succeeding log level also gives you all the more severe log levels before it. For example, if set to WARNING, only CRITICAL, ERROR, and WARNING level log entries are logged. If set to DEBUG, all levels are logged.


    Maximum number of log files in the log directory. The default is "10". Before the system tries to create the 11th log, it runs the clean up routine to purge old log files.


    Maximum disk space in bytes for all log files. The default is "2097152". When creating the next log file will violate this limit, the system tries to free disk space by deleting the oldest logs.


    Minimum free disk space (in bytes) that must be available for logging. When this value is reached, Calendar Server attempts to free disk space by expiring old log files. Logging is paused if space cannot be freed up. The default is "5242880".


    Name of the log file for the csnotifyd service. The default is "notify.log".


    Number of seconds before the log files are rotated. That is, the time interval between creation opening of new log files. The default is "86400".

    Name of the log file for the calendar store. The default is "store.log".

  5. Save the file as ics.conf.

  6. Restart Calendar Server.


See Also

To configure transaction logging for the calendar database, see Chapter 9, Configuring Automatic Backups (csstored).

You do not have to configure the delete log (for deleted events and tasks). See Chapter 18, Administering the Delete Log Database.