multilog exits 0 when it sees the end of stdin. If stdin has a partial final line then multilog inserts a final newline.
multilog writes a message to stderr and exits 111, without reading any input, if it runs out of memory or if another multilog process is writing to one of the same automatically rotated logs.
If multilog has trouble writing to disk after it starts reading input, it writes a message to stderr, pauses, and tries again, without losing any data. Note that this may block any program feeding input to multilog.
If multilog receives a TERM signal, it will read and process data until the next newline, and then exit, leaving stdin at the first byte of data it has not processed.
pattern is a string of stars and non-stars. It matches any concatenation of strings matched by all the stars and non-stars in the same order. A non-star matches itself. A star before the end of pattern matches any string that does not include the next character in pattern. A star at the end of pattern matches any string.
For example, the action
+hello
selects hello. It does not select hello world.
The action
-named[*]: Cleaned cache *
deselects named[135]: Cleaned cache of 3121 RRs. The first star matches any string that does not include a right bracket.
The action
-*
deselects every line.
To save memory, multilog actually checks pattern against only the first 1000 characters of each line.
For example, the sequence of actions
-*
+STAT*
=log/status
maintains log/status as a copy of the most recent line starting with STAT.
Patterns apply to the line after the timestamp is inserted. For example, if
multilog t '-*' '+* fatal: *' ./main
reads the line
fatal: out of memory
then it will log a line such as
@400000003b4a39c23294b13c fatal: out of memory
with the first * matching the timestamp.
You can use tai64nlocal(8) to convert these timestamps to human-readable form.
Do not attempt to write to one log from two simultaneous multilog processes, or two actions in one process.
The log format is as follows. dir is a directory containing some number of old log files, a log file named current, and other files for multilog to keep track of its actions. Each old log file has a name beginning with @, continuing with a precise timestamp showing when the file was finished, and ending with one of the following codes:
Beware that NFS, async filesystems, and softupdates filesystems may discard files that were not safely written to disk before an outage.
While multilog is running, current has mode 644. If multilog sees the end of stdin, it writes current safely to disk, and sets the mode of current to 744. When it restarts, it sets the mode of current back to 644 and continues writing new lines.
When multilog decides that current is big enough, it writes current safely to disk, sets the mode of current to 744, and renames current as an old log file. The action
In versions 0.75 and above: If multilog receives an ALRM signal, it immediately decides that current is big enough, if current is nonempty. The action
http://cr.yp.to/daemontools.html