Displaying 14 results from an estimated 14 matches for "log_flushed".
Did you mean:
log_flush
2014 Nov 02
2
Re: KVM incremental backup using CBT
...#39;SHOW ENGINE INNODB STATUS \G'
+ mysql -uroot -ppassword
++ grep 'Log sequence number' /tmp/mysql-flush.eTdvA4 tr -s ' '
++ cut '-d ' -f4
+ LOG_CURRENT=12242169543
++ grep 'Log flushed up to' /tmp/mysql-flush.eTdvA4 tr -s ' '
++ cut '-d ' -f7
+ LOG_FLUSHED=12242169543
+ '[' 12242169543 = 12242169543 ']'
+ break
+ rm -f /tmp/mysql-flush.eTdvA4
Sun 2 Nov 13:46:14 CET 2014: /etc/qemu/fsfreeze-hook.d/mysql-flush finished
with status=0
Sun 2 Nov 13:46:14 CET 2014: execute /etc/qemu/fsfreeze-hook.d/mysql-flush
thaw
+ MYSQL='mysql -u...
2001 Sep 27
2
Icecast2 in xiph CVS, PATCH!
Hi! Here are some patches to the CVS (ices) that I made to
get my radio webinterface with songselection-support
working.
To make the log update (flush) each time something is
written (before the patch it flushes only when you quit):
---- CUT ----
Index: log.c
============================================================
=======
RCS file: /usr/local/cvsroot/log/log.c,v
retrieving revision
2005 Feb 20
2
ices2 not re-connecting on live stream
On Sun, 2005-02-20 at 12:15, Fr?d?ric Bri?re wrote:
> I've been running ices2 like this 24/7 for months now, only restarting
> it once a week for log rotation. Never had a problem since.
setting <logsize> will cause an automatic log rotation when a certain
file size has been reached. It renames <logfile> to <logfile>.1 then
opens a new file <logfile>
karl.
2005 Feb 20
0
ices2 not re-connecting on live stream
On Sun, Feb 20, 2005 at 08:15:42PM +0000, Karl Heyes wrote:
> setting <logsize> will cause an automatic log rotation when a certain
> file size has been reached. It renames <logfile> to <logfile>.1 then
> opens a new file <logfile>
Since all my other logs are rotated on a daily/weekly basis, I want my
ices logs to behave in the same way.
Nevertheless, this thread
2019 Mar 26
0
[PATCH nbdkit v4 08/15] log: Log extents requests.
Typical output:
2019-03-26 18:22:17.287434 connection=2 Extents id=2 offset=0x0 count=0x40000000 req_one=1 ...
2019-03-26 18:22:17.290040 connection=2 ...Extents id=2 extents=[{ offset=0x0, length=0x250000, type=0 }, { offset=0x250000, length=0x7db0000, type=3 }, { offset=0x8000000, length=0x8000, type=0 }, { offset=0x8008000, length=0x38000, type=3 }, { offset=0x8040000, length=0x208000, type=0
2019 Mar 28
0
[PATCH nbdkit v5 FINAL 09/19] log: Log extents requests.
Typical output:
2019-03-26 18:22:17.287434 connection=2 Extents id=2 offset=0x0 count=0x40000000 req_one=1 ...
2019-03-26 18:22:17.290040 connection=2 ...Extents id=2 extents=[{ offset=0x0, length=0x250000, type=0 }, { offset=0x250000, length=0x7db0000, type=3 }, { offset=0x8000000, length=0x8000, type=0 }, { offset=0x8008000, length=0x38000, type=3 }, { offset=0x8040000, length=0x208000, type=0
2018 Jan 28
0
[nbdkit PATCH 2/2] filters: Add log filter
'nbdkit -v' is quite verbose, and traces everything. Sometimes,
we want to trace JUST the client interactions. In particular, when
debugging another filter, being able to trace what the filter called
can be quite useful; and having the log filter in place will make
it easier to add testsuite coverage of other filters. Also, it is
nice to have timestamps in the log, in order to see if
2014 Oct 29
2
Re: KVM incremental backup using CBT
On 10/29/2014 01:07 PM, Thomas Stein wrote:
> About the --quiesce option. Do i need to do something inside the vm? The most
> commonly would probably be a sql server running inside the vm. Do i need to
> tell the sql server something about the --quiesce option i use? I read this
> article here which suggests such a procedure. Okay, it's vmware, but... Is
> that right?
For
2007 Feb 12
0
[867] trunk/wxruby2/doc/textile/log.txtl: Fix methods section, organise instance and class methods
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2018 Jan 28
3
[nbdkit PATCH 0/2] RFC: tweak error handling, add log filter
Here's what I'm currently playing with; I'm not ready to commit
anything until I rebase my FUA work on top of this, as I only
want to break filter ABI once between releases.
Eric Blake (2):
backend: Rework internal/filter error return semantics
filters: Add log filter
TODO | 2 -
docs/nbdkit-filter.pod | 84 +++++++--
docs/nbdkit.pod
2018 Feb 01
6
[nbdkit PATCH v2 0/3] add log, blocksize filters
Since v1: add the blocksize filter, add testsuite coverage of the
log filter, several fixes to the log filter based on what adding
tests revealed
I'm still working on FUA flag support patches on top of this;
the patches should all be committed in the same release, as we
want to minimize the number of releases that cause a filter
ABI/API bump
Eric Blake (3):
backend: Rework internal/filter
2019 Mar 28
32
[PATCH nbdkit v5 FINAL 00/19] Implement extents.
This has already been pushed upstream. I am simply posting these here
so we have a reference in the mailing list in case we find bugs later
(as I'm sure we will - it's a complex patch series).
Great thanks to Eric Blake for tireless review on this one. It also
seems to have identified a few minor bugs in qemu along the way.
Rich.
2019 Mar 26
21
[PATCH nbdkit v4 00/15] Implement Block Status.
I'm not sure exactly which version we're up to, but let's say it's
version 4.
I'm a lot happier with this version:
- all filters have been reviewed and changed where I think that's necessary
- can_extents is properly defined and implemented now
- NBD protocol is followed
- I believe it addresses all previous review points where possible
The "only" thing
2018 Mar 08
19
[nbdkit PATCH v3 00/15] Add FUA support to nbdkit
After more than a month since v2 [1], I've finally got my FUA
support series polished. This is all of my outstanding patches,
even though some of them were originally posted in separate
threads from the original FUA post [2], [3]
[1] https://www.redhat.com/archives/libguestfs/2018-January/msg00113.html
[2] https://www.redhat.com/archives/libguestfs/2018-January/msg00219.html
[3]