search for: testflag

Hello, first of all i am not sure wheter this is a correct behavior according to the RFC or not... Problem is, when i set a new custom permanent flag (e.g. testflag) and remove it afterwards, the flag still stays in the list of the permanent flags of this drawer even if there are no messages left with this flag set. So the keyword list gets "polluted" with unused flags. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS A...

Hi there, I found that with an IMAP command like <unique-leader> STORE 1 +FLAGS (testflag) I can set arbitrary flags on mails through the dovecot IMAP daemon. This rules. Now I wonder, however, how I can remove those flags, which become properties of the folder, really. For instance, after the above, SELECT on the containing folder gives: * FLAGS (\Answered \Flagged \Deleted \Seen \D...

...ays adds this. We want our normal build to be as # strict as the strictest OS we support, so adding this here # allows us to find problems on our development hosts faster. # It also results in faster load time. conf.env.asneeded_ldflags = conf.ADD_LDFLAGS('-Wl,--as-needed', testflags=True) # MY_MODIFICATION ... my_libs = os.getenv(MY_LDFLAGS') conf.ADD_LDFLAGS(my_libs, testflags=False) # ... MY_MODIFICATION if not conf.CHECK_NEED_LC("-lc not needed"): conf.ADD_LDFLAGS('-lc', testflags=False) and in all the previous releases...

....orig 2005-06-09 12:56:34.000000000 -0500 +++ tools/xenstore/Makefile 2005-06-09 13:48:06.000000000 -0500 @@ -20,6 +20,9 @@ BASECFLAGS+= -I. CFLAGS+=$(BASECFLAGS) +ifeq ($(XEN_TARGET_ARCH),x86_64) +CFLAGS += -fPIC +endif LDFLAGS=$(PROFILE) -L$(XEN_LIBXC) TESTDIR=`pwd`/testsuite/tmp TESTFLAGS=-DTESTING -- Jerone Young IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am trying to install samba 4 on a CentOS 5.6 X86_64 with all update installed following the directions from http://wiki.samba.org/index.php/Samba4/HOWTO Installed git and am able to use that to pull down latest version of samba source code ran ./configure.developer (can post output from this long file if needed) Once that was done I ran the make command and got this at the end

...106 ++++++++++++++++++++++++++++++++++++++- 2 files changed, 105 insertions(+), 3 deletions(-) diff -r d2bf1a7cc131 -r 2353a28247b1 tools/xenstore/Makefile --- a/tools/xenstore/Makefile Sat Jul 29 14:05:59 2006 +0100 +++ b/tools/xenstore/Makefile Tue Aug 01 08:47:33 2006 -0400 @@ -26,7 +26,7 @@ TESTFLAGS= -DTESTING TESTFLAGS= -DTESTING TESTENV = XENSTORED_ROOTDIR=$(TESTDIR) XENSTORED_RUNDIR=$(TESTDIR) -CLIENTS := xenstore-exists xenstore-list xenstore-read xenstore-rm +CLIENTS := xenstore-exists xenstore-list xenstore-read xenstore-rm xenstore-chmod CLIENTS += xenstore-write CLIENTS_OBJS :=...

Hi, dovecot-sieve-1.1.2 + dovecot-1.1.beta13 segfaults with the following sieve filter: --- require ["imapflags"]; if header :contains "subject" ["test"] { addflag "$testflag"; } --- when a message with a subject containing "test" is delivered via dovecot lda. The fault backtrace is: (gdb) run Starting program: /usr/local/libexec/dovecot/deliver -d load1 at virt1.cti2.com < bad.txt Program received signal SIGSEGV, Segmenta...

...E_DIR)\" FLAGS = -O -DHAVE_CONFIG_H -D_SAMBA_BUILD_ -D_LARGEFILE64_SOURCE FLAGS += -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE CIFLAGS=-Iinclude/ -I. -Ipopt/ -Insswitch/ DYNEXP=-Wl,--export-dynamic LDFLAGS=-L/lib LIBS= -ldl #### LIBS_SMBD= -lcrypt -ldl -lresolv LIBS_NMBD= -ldl -lresolv TESTFLAGS= -O -Ipopt -Iinclude -Itdb $(FLAGS) -I. CFLAGS= $(CWFLAGS) $(COFLAGS) $(CIFLAGS) $(APPFLAGS) $(FLAGS) SRC_SMBD=smbd/mangle.c smbd/process.c smbd/conn.c smbd/quotas.c \ smbd/statcache.c smbd/uid.c smbd/service.c smbd/negprot.c \ smbd/password.c smbd/connection.c smbd/sec_ctx.c smbd/session.c...

Hi. I'm making calls via the Manager OriginateAction. My action is set to be async and therefore I receive originiate events. Within the originate event that I receive there is a reason code. In the event of failure I need to dermine why the call failed (no pickup, rejected, no such number, circuit busy, ect) and inform the user with a meaningful message. I assume that one is suppose to

...ils.o -xs_watch_stress: xs_watch_stress.o xs_test_lib.o xs_lib.o talloc.o utils.o -xs_test.o xs_stress.o xs_watch_stress.o xenstored_core_test.o xenstored_watch_test.o xenstored_transaction_test.o xenstored_domain_test.o xs_random.o xs_test_lib.o talloc_test.o fake_libxc.o: CFLAGS=$(BASECFLAGS) $(TESTFLAGS) +xs_test.o xs_stress.o xenstored_core_test.o xenstored_watch_test.o xenstored_transaction_test.o xenstored_domain_test.o xs_random.o xs_test_lib.o talloc_test.o fake_libxc.o: CFLAGS=$(BASECFLAGS) $(TESTFLAGS) xenstored_%_test.o: xenstored_%.c $(COMPILE.c) -o $@ $< @@ -66,7 +65,7 @@ cle...

This patch set adds XSM security labels to useful debugging output locations, and fixes some assumptions that all interrupts behaved like GSI interrupts (which had useful non-dynamic IDs). It also cleans up the policy build process and adds an example of how to use the user field in the security context. Debug output: [PATCH 01/10] xsm: Add security labels to event-channel dump [PATCH 02/10] xsm: