search for: logappend

Always truncating a log can wipe out useful history. Add an option to change this. Signed-off-by: Eric Blake <eblake@redhat.com> --- Hmm - logappend=false enables appending. Maybe we need a common utility function for parsing bool values (parse 0 and case-insensitive "off" or "false" as off, all others as true, or even report values that can't be parsed reasonably) filters/log/nbdkit-log-filter.pod | 5 +++-- filters/l...

...log-filter.pod index 0903329..cff209e 100644 --- a/filters/log/nbdkit-log-filter.pod +++ b/filters/log/nbdkit-log-filter.pod @@ -4,7 +4,7 @@ nbdkit-log-filter - nbdkit log filter =head1 SYNOPSIS - nbdkit --filter=log plugin logfile=FILE [plugin-args...] + nbdkit --filter=log plugin logfile=FILE [logappend=BOOL] [plugin-args...] =head1 DESCRIPTION @@ -22,7 +22,8 @@ work even when nbdkit is run as a daemon. The nbdkit-log-filter requires a single parameter C<logfile> which specifies the path of the file to use for logging. If the file -already exists, it will be truncated. +already exists...

v2 turned out to be much more involved, as I ended up fixing several things along the way that I noticed while debugging a feature addition. Eric Blake (5): maint: Improve ./nbdkit option parsing main: Saner newline printing during --help utils: Add nbdkit_parse_bool main: Use new bool parser for --tls log: Allow user option of appending to log docs/nbdkit-plugin.pod | 11

...nformation. - tests: Use a helper function to refactor and simplify most tests. - partition filter: Can handle > 128 GPT partitions. - nbdkit can be compiled on the Haiku operating system (François Revol). - New nbdkit_parse_bool API for parsing boolean parameters (Eric Blake). - log: Add logappend=[true|false] (Eric Blake). - ocaml: New set_error and debug calls. - Analyze code under AddressSanitizer and ThreadSanitizer and fix bugs (Eric Blake). - Analyze code under Coverity and fix bugs. - Tests now run more quickly. Rich. -- Richard Jones, Virtualization Group, Red Hat http://pe...

Hi, Ever since I recently upgraded to Fedora 25, I can't get kvm working. It's worked on this system since initial fedora 20 install. All upgrades were done via yum, then once available, dnf. I do have libvirt-sock in LISTENING state: STREAM LISTENING /var/run/libvirt/libvirt-sock I noticed I also have multiple connections in CONNECTING state: STREAM CONNECTING 0

...nectHost = 0x0, connectService = 0x0}, nix = {path = 0x7fcd34151d90 >"/var/lib/libvirt/qemu/capabilities.monitor.sock", listen = false}, >spicevmc = 873799056, spiceport = {channel = 0x7fcd34151d90 >"/var/lib/libvirt/qemu/capabilities.monitor.sock"}}, logfile = 0x0, >logappend = 0} > monpath = 0x7fcd34151d90 >"/var/lib/libvirt/qemu/capabilities.monitor.sock" > pidfile = 0x7fcd341ad8b0 >"/var/lib/libvirt/qemu/capabilities.pidfile" > xmlopt = 0x0 >#6 virQEMUCapsNewForBinaryInternal (binary=binary@entry=0x7fcd34...

...ectService = 0x0}, nix = {path = 0x7fcd34151d90 >> "/var/lib/libvirt/qemu/capabilities.monitor.sock", listen = false}, >> spicevmc = 873799056, spiceport = {channel = 0x7fcd34151d90 >> "/var/lib/libvirt/qemu/capabilities.monitor.sock"}}, logfile = 0x0, >> logappend = 0} >> monpath = 0x7fcd34151d90 >> "/var/lib/libvirt/qemu/capabilities.monitor.sock" >> pidfile = 0x7fcd341ad8b0 >> "/var/lib/libvirt/qemu/capabilities.pidfile" >> xmlopt = 0x0 >> #6 virQEMUCapsNewForBinaryInternal (b...