aboutgitcodebugslistschat
path: root/test/run
diff options
context:
space:
mode:
authorStefano Brivio <sbrivio@redhat.com>2022-10-06 14:51:04 +0200
committerStefano Brivio <sbrivio@redhat.com>2022-10-14 17:38:28 +0200
commit01efc71ddd2523594b94e8be00d9e51d6cdd6130 (patch)
treee95bd46620cd1669b02fafbfda0b9da40fd35268 /test/run
parentf4e1e88e1dce3a25f3cdd8d52a1f097236911e70 (diff)
downloadpasst-01efc71ddd2523594b94e8be00d9e51d6cdd6130.tar
passt-01efc71ddd2523594b94e8be00d9e51d6cdd6130.tar.gz
passt-01efc71ddd2523594b94e8be00d9e51d6cdd6130.tar.bz2
passt-01efc71ddd2523594b94e8be00d9e51d6cdd6130.tar.lz
passt-01efc71ddd2523594b94e8be00d9e51d6cdd6130.tar.xz
passt-01efc71ddd2523594b94e8be00d9e51d6cdd6130.tar.zst
passt-01efc71ddd2523594b94e8be00d9e51d6cdd6130.zip
log, conf: Add support for logging to file
In some environments, such as KubeVirt pods, we might not have a system logger available. We could choose to run in foreground, but this takes away the convenient synchronisation mechanism derived from forking to background when interfaces are ready. Add optional logging to file with -l/--log-file and --log-size. Unfortunately, this means we need to duplicate features that are more appropriately implemented by a system logger, such as rotation. Keep that reasonably simple, by using fallocate() with range collapsing where supported (Linux kernel >= 3.15, extent-based ext4 and XFS) and falling back to an unsophisticated block-by-block moving of entries toward the beginning of the file once we reach the (mandatory) size limit. While at it, clarify the role of LOG_EMERG in passt.c. Signed-off-by: Stefano Brivio <sbrivio@redhat.com> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'test/run')
0 files changed, 0 insertions, 0 deletions