Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Kiwi Syslog Server > Kiwi Sys - Knowledgebase Articles > Kiwi Syslog setting up Unix machine

Kiwi Syslog setting up Unix machine

Table of contents

Updated: August 24, 2016


This is how you set up a Unix machine to send syslog messages on Kiwi Syslog Server.


  • All versions of Kiwi Syslog


Note: With a Unix host, you need super user privileges to modify the files following files:

  1. Restart (HUP) the Syslog Server on the Unix box.
  2. Use vi or any text file editor of your choice to modify the /etc/hosts file. Sample hosts file:

    # Internet host table
    #                localhost        loghost

    This allows you to use the hostname loghost to direct your messages to. 
    The IP address used for loghost should be the IP address of the Windows or NT box you are running Kiwi Syslog Server on.
  3. Use vi or any text file editor of your choice to modify the /etc/syslog.conf file. Sample syslog.conf file:

    # Syslog configuration file.


    *.err;kern.notice;auth.notice                        /dev/console

    *.err;kern.debug;daemon.notice;mail.crit        /var/adm/messages


    *.alert;kern.err;daemon.err                        operator

    *.alert                                                root


    *.emerg                                                @loghost

    mail.debug                                                @loghost

    You will notice that all facilities with a level of emerg will be forwarded to the loghost (defined in the hosts file) and any mail alerts with a level of debug will also be forwarded.

  4. The general idea is Facility.Level <TAB> @loghost

  5. Save this file after editing and restart the Syslog Server on the Unix box for it to take effect.
  6. Find the syslog Server process ID, and send it a SIGHUP signal.
  7. Test if the syslog server is writing messages using the logger command, such as logger –p user.emerg Unix test message.
  8. If in doubt resort to man syslogd.



Last modified