search for: log_flush

...#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...

...9/10 02:32:03 1.1.1.1 +++ log.c 2001/09/27 06:16:00 @@ -161,7 +161,8 @@ snprintf(pre, 256, "%s %s", prior[priority-1], cat); - fprintf(loglist[log_id].logfile, "%s %s %s\n", tyme, pre, line); + fprintf(loglist[log_id].logfile, "%s %s %s\n", tyme, pre, line); + log_flush(log_id); va_end(ap); } @@ -178,7 +179,7 @@ fprintf(loglist[log_id].logfile, "%s\n", line); va_end(ap); - fflush(loglist[log_id].logfile); + log_flush(log_id); } int _get_log_id() ---- CUT --- To make ices restart playing the playlist from the beginning when it is updated:...

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.

...ond LOG_INFO0, apart from verboseness, ensures that the new logfile is created right away.) --- ices2-2.0.0-kh59.orig/src/signals.c +++ ices2-2.0.0-kh59/src/signals.c @@ -51,9 +51,11 @@ void signal_hup_handler(int signum __attribute__((unused))) { LOG_INFO0("Flushing logs"); - log_flush(ices_config->log_id); + log_reopen(ices_config->log_id); + LOG_INFO0("Reloading playlist"); ices_config->next_track = 1; + signal(SIGHUP, signal_hup_handler); } @@ -67,6 +69,7 @@ void signals_setup(void) { + signal(SIGHUP, signal_hup_handler); signal(SI...

...tents_str : "(null)"); + free (extents_str); + } + return r; +} + static struct nbdkit_filter filter = { .name = "log", .longname = "nbdkit log filter", @@ -370,6 +414,7 @@ static struct nbdkit_filter filter = { .flush = log_flush, .trim = log_trim, .zero = log_zero, + .extents = log_extents, }; NBDKIT_REGISTER_FILTER(filter) -- 2.20.1

...tents_str : "(null)"); + free (extents_str); + } + return r; +} + static struct nbdkit_filter filter = { .name = "log", .longname = "nbdkit log filter", @@ -370,6 +414,7 @@ static struct nbdkit_filter filter = { .flush = log_flush, .trim = log_trim, .zero = log_zero, + .extents = log_extents, }; NBDKIT_REGISTER_FILTER(filter) -- 2.20.1

...flags & ~fua)) */ + output (h, "Write", id, "offset=0x%" PRIx64 " count=0x%x fua=? ...", + offs, count); + r = next_ops->pwrite (nxdata, buf, count, offs); + output_return (h, "...Write", id, r); + return r; +} + +/* Flush. */ +static int +log_flush (struct nbdkit_next_ops *next_ops, void *nxdata, void *handle) +{ + struct handle *h = handle; + uint64_t id = get_id (h); + int r; + + /* TODO expose flags to filters */ + /* assert (!flags) */ + output (h, "Flush", id, "..."); + r = next_ops->flush (nxdata); + outpu...

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

...reate new log targets on the fly if there is none -currently. (Almost) for internal use only: it is supposed to be called by the -application shutdown code. - -Note that this function also calls -"clear_trace_masks":#Log_cleartracemasks. - </del><span class="cx"> h3(#Log_flush). Log#flush </span><span class="cx"> </span><span class="cx"> *flush*() </span></span></pre> </div> </div> </body> </html>

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

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

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.

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

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]