The cc-config command lets you modify the selected settings that the Control Center uses. These settings include Content Filtering Audit logs, port 443 access, and more.
Change the log level of the main Control Center log, BrightmailLog.log.
When you apply this to the Control Center log, cc-config writes the command-line parameters to the log4j properties file. It then restarts the Control Center.
Change the rollover frequency of the Content Filtering log.
List, optimize, validate, or repair the database tables that the Control Center uses.
Ensure that you validate the database using the cc-config database --check command before updating your Symantec Messaging Gateway. If there are any errors in the tables, repair the erroneous tables using cc-config database --repair [tableName] command and then update your Symantec Messaging Gateway.
Turn on or off access to the Control Center using HTTP and port 41080.
If http access is off, you cannot access the Control Center with a URL that starts with http://. If http access is on, you can access the Control Center with a URL that starts with http://. To access the Control Center using http, append :41080 to the URL. Regardless of the http setting, you can always access the Control Center with a URL that starts with https://. Unlike HTTPS, HTTP is not a secure protocol, so the communication between your Web browser and the Control Center could be monitored by a third party.
Enables support for TLS 1.1 for the Control Center and restarts the Control Center. After enabling TLS 1.1, you cannot access the Control Center using a browser that does not support TLS encryption.
Turn on or off access to the Control Center using HTTPS and port 443 (the standard, SSL-secured port for Web servers).
When port 443 access is off, you must append :41443 to the URL when you use an https:// URL to access the Control Center. When port 443 access is enabled, you do not need to append the port number for an https:// URL to access the Control Center.
Check the given database table. If no table name is specified, then check all tables.
Set the number of days to keep logs before they roll over.
Display this message.
Set the log level. The log levels are listed below from least verbose to most verbose and each level includes the previous level. For example, if you specify the errors level, only the most urgent log messages are stored. If you specify the debug level, errors, warnings, information and debug level log messages are stored.
Specify one of the following log levels:
Disable a feature.
Enable a feature.
Optimize the table so it takes less space on disk. If no table name is specified, then optimize all tables.
Repair the given database table. If no table name is specified, then attempt a repair operation on all damaged tables.
Display the current log settings and port statuses.
Imported Document ID: HOWTO92634
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe