RSyslog Documentation

imtuxedoulog: Tuxedo ULOG input module

Module Name:imtuxedoulog
Authors:Jean-Philippe Hilaire <> & Philippe Duveau <>


This module allows rsyslog to process Tuxedo ULOG files. Tuxedo create an ULOG file each new log of the day this file is defined

  • a prefix configured in the tuxedo configuration
  • a suffix based on the date “.MMDDYY”

This module is a copy of the polling mode of imfile but the file name is computed each polling. The previous one is closed to limit the number of opened file descriptor simultaneously.

Another particularity of ULOG is that the lines contains only the time in day. So the module use the date in filename and time in log to fill log timestamp.


To successfully compile improg module.

./configure –enable-imtuxedoulog …

Configuration Parameters

Action Parameters


stringyespath of ULOG file 

Path of ULOG file as it is defined in Tuxedo Configuration ULOGPFX. Dot and date is added a end to build full file path


stringyes none

The tag to be assigned to messages read from this file. If you would like to see the colon after the tag, you need to include it when you assign a tag value, like so: tag="myTagValue:".



The syslog facility to be assigned to messages read from this file. Can be specified in textual form (e.g. local0, local1, …) or as numbers (e.g. 16 for local0). Textual form is suggested.



The syslog severity to be assigned to lines read. Can be specified in textual form (e.g. info, warning, …) or as numbers (e.g. 6 for info). Textual form is suggested.


typedefaultmandatoryobsolete legacy directive

Specifies how often the state file shall be written when processing the input file. The default value is 0, which means a new state file is only written when the monitored files is being closed (end of rsyslogd execution). Any other value n means that the state file is written every time n file lines have been processed. This setting can be used to guard against message duplication due to fatal errors (like power fail). Note that this setting affects imfile performance, especially when set to a low value. Frequently writing the state file is very time consuming.


typedefaultmandatoryobsolete legacy directive

If set to 0, the file will be fully processed. If it is set to any other value, a maximum of [number] lines is processed in sequence. The default is 10240.


typedefaultmandatoryobsolete legacy directive

This is an expert option. It can be used to set the maximum input batch size that the module can generate. The default is 1024, which is suitable for a wide range of applications. Be sure to understand rsyslog message batch processing before you modify this option. If you do not know what this doc here talks about, this is a good indication that you should NOT modify the default.

See also

Help with configuring/using Rsyslog:

  • Mailing list - best route for general questions
  • GitHub: rsyslog source project - detailed questions, reporting issues that are believed to be bugs with Rsyslog
  • Stack Exchange (View, Ask) - experimental support from rsyslog community

See also

Contributing to Rsyslog:

Copyright 2008-2020 Rainer Gerhards (Großrinderfeld), and Others.

Scroll to top