search for: reopened

Displaying 20 results from an estimated 2320 matches for "reopened".

2016 Jun 08
2
Allow reopening on Phabricator
...t; > > > I have wanted to reopen a Phabricator revision too many times already, > > but couldn’t. I don’t know who the admin of reviews.llvm.org > > <http://reviews.llvm.org> is (CC’ing Chandler as my wild guess). Could > > we configure it so that revisions can be reopened? > > Manuel is the one to CC. > > Tobias > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160608/18d13b70/attachment.html>
2019 Sep 19
0
[PATCH nbdkit v3 3/3] retry: Add a test of this filter.
We use a custom sh plugin to test retries are working. --- tests/Makefile.am | 8 +++ tests/test-retry-reopen-fail.sh | 108 ++++++++++++++++++++++++++++++++ tests/test-retry.sh | 97 ++++++++++++++++++++++++++++ 3 files changed, 213 insertions(+) diff --git a/tests/Makefile.am b/tests/Makefile.am index 1b1e05b..af9b9d9 100644 --- a/tests/Makefile.am +++
2019 Sep 19
1
Re: [PATCH nbdkit v2 2/4] filters: Implement next_ops .reopen call.
On 9/19/19 9:33 AM, Richard W.M. Jones wrote: > This is intended for use by the forthcoming retry filter to close and > reopen the backend chain. It is handled entirely by server/backend.c > as no cooperation is needed with the plugin. > > Note the explicit readonly parameter: An alternative would be to store > the previous readonly setting in the b_conn_handle struct. However
2011 Oct 18
1
"doveadm log reopen" don't reopen separate lmtp log
I still see the issue below. Is there anyone running separate LMTP logging that could check if they experience the same issue? Best regards Henrik Larsson -------- Original Message -------- Subject: "doveadm log reopen" don't reopen separate lmtp log Date: Sun, 25 Sep 2011 00:23:49 +0200 From: Henrik Larsson <dovecot-user at spambox.dk> To: dovecot at dovecot.org Dear all
2019 Sep 19
2
Re: [PATCH nbdkit v3 3/3] retry: Add a test of this filter.
On 9/19/19 10:26 AM, Richard W.M. Jones wrote: > We use a custom sh plugin to test retries are working. > --- > tests/Makefile.am | 8 +++ > tests/test-retry-reopen-fail.sh | 108 ++++++++++++++++++++++++++++++++ > tests/test-retry.sh | 97 ++++++++++++++++++++++++++++ > 3 files changed, 213 insertions(+) > > +++
2019 Sep 19
1
Re: [PATCH nbdkit v3 1/3] filters: Implement next_ops .reopen call.
On 9/19/19 10:26 AM, Richard W.M. Jones wrote: > This is intended for use by the forthcoming retry filter to close and > reopen the backend chain. It is handled entirely by server/backend.c > as no cooperation is needed with the plugin. > > Note the explicit readonly parameter: An alternative would be to store > the previous readonly setting in the b_conn_handle struct.
2019 Oct 07
6
[nbdkit PATCH 0/5] More retry fixes
I think this is my last round of patches for issues I identified with the retry filter. With this in place, it should be safe to interject another filter in between retry and the plugin. Eric Blake (5): retry: Don't call into closed plugin tests: Refactor test-retry-reopen-fail.sh tests: Enhance retry test to cover failed reopen server: Move prepare/finalize/close recursion to
2016 Jun 07
2
Allow reopening on Phabricator
...y modified version of your original patch ... I have wanted to reopen a Phabricator revision too many times already, but couldn’t. I don’t know who the admin of reviews.llvm.org <http://reviews.llvm.org/> is (CC’ing Chandler as my wild guess). Could we configure it so that revisions can be reopened? Kuba -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160607/90fe37bc/attachment.html>
2011 Sep 24
0
"doveadm log reopen" don't reopen seperate lmtp log
Dear all I have setup separate pop3/imap log "/var/log/dovecot" and lmtp delivery log "/var/log/dovecot-deliver". After rotating logfiles, i run "doveadm log reopen". I see that my pop3/imap log "/var/log/dovecot" is used straight away, but my lmpt log "/var/log/dovecot-deliver" isn't used at first. After some time, usually a few minutes,
2019 Sep 19
7
[PATCH nbdkit v3 0/3] Add new retry filter.
v2 was here: https://www.redhat.com/archives/libguestfs/2019-September/msg00221.html I think this is more like "the one". It handles reopen failing correctly, and there is a second test for that. I also ran my sshd tests locally and it worked in all scenarios I could think up (except of course sshd not being available at the start, but we want that to fail). Rich.
2019 Jul 08
3
Orphaned processes after doveadm log reopen
I rotate logs every night on my Director, running "doveadm log reopen" I've noticed a problem with processes not closing correctly, they can be open for days and cause corrupt index files because they are connected to different backends (so it writes to the wrong server when the process disconnects) 23518 ? S 140:53 dovecot/anvil [4 connections] 23519 ? S
2006 May 20
2
xapian-tcpsrv need to reopen database?
Hi, I'm adapting the omega (in a Python way ;) to do search across multiple remotes database, for now, I have only one xapian-tcpsrc running, but I have documents being inserted at the same time, so (like I have readed in others e-mails) the xapian-tcpsrc throw the following message: Connection from 192.168.0.101, port 64161 Got exception DatabaseModifiedError: The revision being read has
2019 Sep 19
0
[PATCH nbdkit v2 2/4] filters: Implement next_ops .reopen call.
This is intended for use by the forthcoming retry filter to close and reopen the backend chain. It is handled entirely by server/backend.c as no cooperation is needed with the plugin. Note the explicit readonly parameter: An alternative would be to store the previous readonly setting in the b_conn_handle struct. However passing it explicitly allows the retry filter to retry as readonly, which
2019 Sep 19
0
[PATCH nbdkit v3 1/3] filters: Implement next_ops .reopen call.
This is intended for use by the forthcoming retry filter to close and reopen the backend chain. It is handled entirely by server/backend.c as no cooperation is needed with the plugin. Note the explicit readonly parameter: An alternative would be to store the previous readonly setting in the b_conn_handle struct. However passing it explicitly allows the retry filter to retry as readonly, which
2012 Dec 19
1
question about trigger of reopen
Hi all, Currently I'm implementing a retrieval system with multiple reader processes and only one writer process updating the database periodically. In a reader process, whenever a Xapian::DatabaseModifiedError exception is caught, I call function reopen() and retry. However, my problem is, when there is only a small set of modification, e.g. only one new document is added, the reader would
2019 Jul 09
1
Orphaned processes after doveadm log reopen
On 8.7.2019 14.54, Tom Sommer via dovecot wrote: > > On 2019-07-08 13:36, Tom Sommer via dovecot wrote: >> I rotate logs every night on my Director, running "doveadm log reopen" > > It happens on "/etc/init.d/dovecot restart", not "doveadm log reopen" > - sorry > > So it happens when you run killproc on dovecot > > --- > Tom Do
2019 Oct 01
0
[nbdkit PATCH 3/6] retry: Check next_ops->can_FOO on retry
After a retry, if the second connection has fewer permissions than the first, but we blindly call next_ops->FOO, we end up triggering an assertion failure in backend.c. This is particularly noticeable when the force_readonly flag is in effect, as that makes it much easier for there to be fewer permissions than before. Add testsuite coverage of pwrite to demonstrate. Signed-off-by: Eric Blake
2015 Aug 21
0
Processed: unarchiving 763102, reopening 763102, forcibly merging 763102 787193
...debian.org>} [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions xen/4.4.0-1. > forcemerge 763102 787193 Bug #763102 [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains Bug #787193 [xen-utils-common] xen-utils-common: xen-init-list crashes with...
2017 Nov 06
2
Log reopen broken in 2.2.33?
Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? Using the same config that I've had for the past 10 or so point releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, but with 2.2.33 (and .1 and .2) no new logfiles are created, file descriptors still have the original files open and keep writings to those logs. On an idling test instance, I get: master:
2004 Aug 06
0
[PATCH] - Make reopening of Log files
independent from Configuration Reload In-Reply-To: <200406161051.03808.msmith@xiph.org> References: <1087307353.28637.11.camel@forge.intermeta.de> <200406161051.03808.msmith@xiph.org> Message-ID: <1087392799.7778.4.camel@forge.intermeta.de> Hi, yes, I tested the patch. Then I sent you the wrong version. I attached the correct one. Yes, this one works. Why just reopening