openbmc/build/tmp/deploy/sdk/witherspoon-2019-08-08/sysroots/armv6-openbmc-linux-gnueabi/usr/src/debug/rsyslog/8.1903.0-r0/rsyslog-8.1903.0/runtime/stream.c
static rsRetVal strmRecordBegin(strm_t* pThis)
{
    assert(pThis != NULL);
    assert(pThis->bInRecord == 0);
    pThis->bInRecord = 1;
    return RS_RET_OK;
}
/* support for data records
 * The stream class is able to write to multiple files. However, there are
 * situation (actually quite common), where a single data record should not
 * be split across files. This may be problematic if multiple stream write
 * calls are used to create the record. To support that, we provide the
 * bInRecord status variable. If it is set, no file spliting occurs. Once
 * it is set to 0, a check is done if a split is necessary and it then
 * happens. For a record-oriented caller, the proper sequence is:
 *
 * strmRecordBegin()
 * strmWrite...()
 * strmRecordEnd()
 *
 * Please note that records do not affect the writing of output buffers. They
 * are always written when full. The only thing affected is circular files
 * creation. So it is safe to write large records.
 *
 * IMPORTANT: RecordBegin() can not be nested! It is a programming error
 * if RecordBegin() is called while already in a record!
 *
 * rgerhards, 2008-01-10
 */
support for data records
The stream class is able to write to multiple files. However, there are
situation (actually quite common), where a single data record should not
be split across files. This may be problematic if multiple stream write
calls are used to create the record. To support that, we provide the
bInRecord status variable. If it is set, no file spliting occurs. Once
it is set to 0, a check is done if a split is necessary and it then
happens. For a record-oriented caller, the proper sequence is.



Please note that records do not affect the writing of output buffers. They
are always written when full. The only thing affected is circular files
creation. So it is safe to write large records.

RecordBegin() can not be nested. It is a programming error
if RecordBegin() is called while already in a record!


support for data records The stream class is able to write to multiple files . However there are situation ( actually quite common ) where a single data record should not be split across files . This may be problematic if multiple stream write calls are used to create the record . To support that we provide the bInRecord status variable . If it is set no file spliting occurs . Once it is set to 0 a check is done if a split is necessary and it then happens . For a record - oriented caller the proper sequence is . Please note that records do not affect the writing of output buffers . They are always written when full . The only thing affected is circular files creation . So it is safe to write large records . RecordBegin () can not be nested . It is a programming error if RecordBegin () is called while already in a record!
static rsRetVal strmRecordBegin(strm_t* pThis)
{
    assert(pThis != NULL);
    assert(pThis->bInRecord == 0);
    pThis->bInRecord = 1;
    return RS_RET_OK;
}
static rsRetVal strmRecordBegin ( strm_t * pThis ) { assert ( pThis != NULL ) ; assert ( pThis -> bInRecord == 0 ) ; pThis -> bInRecord = 1 ; return RS_RET_OK ; }
support for data records
 The stream class is able to write to multiple files.
support for data records The stream class is able to write to multiple files .