.TH "appender_type_mmap.h" 3 "Mon May 2 2011" "Version 1.2.1" "log4c" \" -*- nroff -*- .ad l .nh .SH NAME appender_type_mmap.h \- .PP Log4c mmap(2) appender interface. .SH SYNOPSIS .br .PP \fC#include \fP .br \fC#include \fP .br .SS "Variables" .in +1c .ti -1c .RI "__LOG4C_BEGIN_DECLS const \fBlog4c_appender_type_t\fP \fBlog4c_appender_type_mmap\fP" .br .in -1c .SH "Detailed Description" .PP Log4c mmap(2) appender interface. The mmap appender uses a fixed length memory mapped file for logging. The appender's name is used as the file name which will be opened and mapped to memory at first use. The memory mapped file is then used as a rotating buffer in which logging events are written. .PP The following examples shows how to define and use mmap appenders. .PP .PP .nf log4c_appender_t* myappender; myappender = log4c_appender_get('myfile.log'); log4c_appender_set_type(myappender, &log4c_appender_type_mmap); .fi .PP .PP \fBWarning:\fP .RS 4 the file is not created at first use. It should already exist and have a reasonable size, a mutilple of a page size. .RE .PP .SH "Variable Documentation" .PP .SS "__LOG4C_BEGIN_DECLS const \fBlog4c_appender_type_t\fP \fBlog4c_appender_type_mmap\fP"Mmap appender type definition. .PP This should be used as a parameter to the \fBlog4c_appender_set_type()\fP routine to set the type of the appender. .SH "Author" .PP Generated automatically by Doxygen for log4c from the source code.