Logging to Syslog

Users prefer Pleasant Password Server with a KeePass client!

Password Server can redirect log events to a Syslog server.

About the Syslog Protocol

The Syslog protocol is a format standard for Event log messages, originally becoming popular first in Unix-based systems.  It is effective for redirecting and filtering system logs or alerts and is useful towards consolidating logs from multiple systems.

It is useful in the administration of these aspects of log messages:

  • Managing system alerts
  • Debugging event messages
  • Tracking information
  • Auditing system security
  • etc.

For more details see:

Enabling Syslog

To enable logging to Syslog, go to:

  • Logging -> Syslog Configuration

Configuration Options

The following options are available:


  • Determines whether messages are sent to your Syslog Server or not.


  • The address of the server running your Syslog Server.


  • The port used by your Syslog server.


  • The transport protocol used to send the Syslog data: UDP or TCP/IP.


  • A facility code specifies the type of program that is logging the message and allows different log sources to be handled in different ways.

In most cases one of the LocalUse values (LocalUser0 thru LocalUser7) can be used for Password Server log events, or another facility value (which you are not already using in your Syslog to indicate another program).

Possible values are:

  • KernelMessages
  • UserLevelMessages
  • MailSystem
  • SystemDaemons
  • InternalMessages
  • LinePrinterSubsystem
  • NetworkNewsSubsystem
  • UUCPSubsystem
  • ClockDaemon1
  • ClockDaemon2
  • FTPDaemon
  • NTPSubsystem
  • LogAudit
  • LogAlert
  • SecurityOrAuthorizationMessages1
  • SecurityOrAuthorizationMessages2
  • LocalUse0
  • LocalUse1
  • LocalUse2
  • LocalUse3
  • LocalUse4
  • LocalUse5
  • LocalUse6
  • LocalUse7