AC Hosting Environment

AC Hosting Environment Documentation
  • 1 Release Notes
    • 1.1 End-Of-Life (EOL) Notice
    • 1.2 Support Policy
    • 1.3 Differences to CentOS
  • 2 Deployment
    • 2.1 Prerequisites
    • 2.2 Preparing to Install
    • 2.3 Installation
    • 2.4 Post Installation Steps
  • 3 AC Tools
    • 3.1 AC Configure Syslog
      • 3.1.1 Introduction
      • 3.1.2 Un/Installation
      • 3.1.3 Usage
    • 3.2 AC Firewall
      • 3.2.1 Introduction
      • 3.2.2 Un/Installation
      • 3.2.3 Usage
    • 3.3 AC Integrity
      • 3.3.1 Introduction
      • 3.3.2 Un/Installation
      • 3.3.3 Usage
      • 3.3.4 Integration Tips
    • 3.4 Make Bash Installer
      • 3.4.1 Introduction
      • 3.4.2 Un/Installation
      • 3.4.3 Usage
    • 3.5 AC X509 Authority
      • 3.5.1 Introduction
      • 3.5.2 Un/Installation
      • 3.5.3 Command Reference
      • 3.5.4 Certificates For Beginners
      • 3.5.5 CA Management
      • 3.5.6 Server, Client, and User Certificate Management
      • 3.5.7 Reporting Commands
      • 3.5.8 Troubleshooting

3.1.3 Usage

September 13th, 2025

AC Configure Syslog is a simple command line tool

3.1.3.1 Basic Syntax

# ac_configure_syslog # ac_configure_syslog datastore <absolute_path> # ac_configure_syslog level <level> <type> [<hostname/IP>|server] # ac_configure_syslog --version

3.1.3.2 Getting the current configuration

# ac_configure_syslog

The above will provide output similar to the following:

DATASTORE=/bear/syslog LOG_LEVEL=medium TYPE=local REMOTE_HOST= SERVER=false

In this example, it tells us that logs are sent to /bear/syslog'; that the logging level is set to medium; that logging is all done locally; that this host is not a Syslog server and will not accept remote log entries.

3.1.3.3 Moving the datastore

It is unlikely that the location of the logging datastore needs to be moved. In most cases this is not recommended. However, if required, the log directory can be moved to any location desired on the system with the following syntax:

# ac_configure_syslog datastore <absolute_path>

Existing logs in the current datastore path will be moved to the new location.

example

# ac_configure_syslog datastore /var/log/new_log_dir

3.1.3.4 Configuring Syslog

# ac_configure_syslog level <level> <type> [<hostname/IP>|server]

level

Controls the logging level, retention and whether the logging is handled locally, sent to a server, or in fact acts as a server for other hosts.

low Logs mainly non-synced event subset for 30 days
medium Logs mostly synced events for 90 days
high Logs mostly synced events for 1 year

type

Indicates whether log events are stored locally on this host or sent to a remote logging server.

local Logs events to local log files
remote Logs events to remote log server specified by the <hostname/IP>

hostname/IP

This is only valid if the <type> is defined as remote. This specifies the location of the logging server. Can be any valid hostname, FQDN, or IP address.

ac_configure_syslog will exist without changes is a supplies hostname or IP address is not reachable over the network from a basic ping test.

server

Optional literal flag only valid if the <type> is local. This specifies that syslog will accept log events from other hosts on the network.

3.1.3.5 Examples

Local logging with retention of one year

# ac_configure_syslog high local

Remote logging

# ac_configure_syslog low remote 192.168.1.40

Remote logging supports any valid remote host address. However, IP addresses are recommended as they do not incur hostname lookups in DNS and are therefore lower latency and utilise fewer resources.

Setting up a Syslog server with a three month event window

# ac_configure_syslog medium local server

previous: Un/Installation next: Introduction