search for: testenv

Hi there, I try to understand the usage of environments but I'm not sure if I get it. I wrote a test script like this: testenv <- new.env(environment()) myfun <- function(x) { print(testvar) testenv$testvar_2 <- 20 } environment(myfun) <- testenv testenv$testvar <- 10 myfun("hello") ls(envir = testenv) Now, I was wondering if there is any way to create new variables in my environment without...

I would like to assign an value to an element of a list contained in an environment. The list will contain vectors and matrices. Here's a simple example: # create toy environment testEnv = new.env(parent = emptyenv()) # create list that will be in the environment, then assign() it x = list(a=1,b=2) assign("xList",x,testEnv) # create new element, to be inserted into xList c = 5:7 Now, what I'd like to do is something like this: assign("xList[[3]]",c,testE...

Kay Sievers wrote: > Hi, > this simple program compiled with klibc: > > #include <stdio.h> > int main(int argc, char* argv[]) > { > setenv("TESTENV", "happy", 1); > printf("TESTENV='%s'\n", getenv("TESTENV")); > } > > prints: > > ./env > TESTENV='(null)' > > > thanks, > Kay Released klibc-0.104 to fix this bug, and in general clean up the se...

...lient m/c to a Samba standalone server (or Samba as member to an AD domain), what are the steps to follow, as I don't see any clear documentation on the same. Below are what I could do so far: samba-4.4.4/selftest/wscript: Main code for selftest samba-4.4.4/selftest/target/--.pm : Files for testenv creation samba-4.4.4/selftest/st: Test environment gets created under this dir Steps followed to execute tests: 1../configure --enable-selftest --testenv 2.make -j testenv SELFTEST_TESTENV=simpleserver 3. make test TESTS=samba3.base *or *make quicktest I c*ould execute "make test"...

...non-interactively and test commits and pull requests against >> the AD. > Then --use-ntvfs and compile with --with-ntvfs-fileserver is the easy > option. > > That will go away some day, then you can follow the examples from our > how we set up our selftest stuff. run 'make testenv' and look in > st/ad_dc/lib/server.conf. > > You may need --enable-developer for this to work. > > Thanks for using Samba and all the best! > > Andrew Bartlett > -- Beste Gr??e Ghassan Elrayah Mail: ghassan.elrayah at live.de

Hi, I am trying to get some integration tests running in CI with a software uses samba4 AD for authentication. So basically I would like spin up a build and provision a samba4 AD with some test users and groups non-interactively and test commits and pull requests against the AD. On 11/14/19 8:16 AM, Andrew Bartlett wrote: > On Thu, 2019-11-14 at 06:19 +0000, Ghassan Elrayah via samba wrote:

Hi, Yes, you're right, the problems are due to the selftest environment failing to start up. In this case, you could just reproduce the same problem with: SELFTEST_TESTENV=s4member:local make testenv There may be some package dependencies you're missing in order to get selftest to run correctly. In a earlier message it looked like you were missing the python DNS package (python-dnspython on ubuntu). It looks like you were still getting dns update errors on this...

...non-interactively and test commits and pull requests against >> the AD. > Then --use-ntvfs and compile with --with-ntvfs-fileserver is the easy > option. > > That will go away some day, then you can follow the examples from our > how we set up our selftest stuff. run 'make testenv' and look in > st/ad_dc/lib/server.conf. > > You may need --enable-developer for this to work. > > Thanks for using Samba and all the best! > > Andrew Bartlett > -- Beste Gr??e Ghassan Elrayah Mail: ghassan.elrayah at live.de

On 11/09/2019 19:36, Andrew Bartlett via samba wrote: > On Wed, 2019-09-11 at 15:14 -0300, Sergio Belkin via samba wrote: >> Hi, >> >> I use AptVanBelle repo for samba, is there a way to backup in unattended >> way (I mean via cron) the DC? >> >> If I use >> samba-tool domain backup online --targetdir=/srv/backup --server= >> samba4.example.com

Hi, When I create an environment object with new.env() and populate it with values then how can I save it into an .RData file properly, so it can be loaded later on in a new session? Saving an environment object with save() or save.image() results in an error message when loading again: Error: protect(): protection stack overflow Regards, benjamin ======================================

Hi, Thanks for the reply, On 4/8/19 12:16 AM, Tim Beale wrote: > Hi, > > Yes, you're right, the problems are due to the selftest environment > failing to start up. In this case, you could just reproduce the same > problem with: > SELFTEST_TESTENV=s4member:local make testenv This actually reveals something: [user at s4member samba]$ ping _kerberos._tcp.dc._msdcs.samba.example.com ERROR: ld.so: object 'libnss_wrapper.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object 'libresol...

On 4/8/2019 12:49 AM, Manfred wrote: >> Hi, >> >> Yes, you're right, the problems are due to the selftest environment >> failing to start up. In this case, you could just reproduce the same >> problem with: >> SELFTEST_TESTENV=s4member:local make testenv > > This actually reveals something: > [user at s4member samba]$ ping _kerberos._tcp.dc._msdcs.samba.example.com > ERROR: ld.so: object 'libnss_wrapper.so' from LD_PRELOAD cannot be > preloaded (cannot open shared object file): ignored. > ERRO...

...ts and pull requests against > > > the AD. > > Then --use-ntvfs and compile with --with-ntvfs-fileserver is the easy > > option. > > > > That will go away some day, then you can follow the examples from our > > how we set up our selftest stuff. run 'make testenv' and look in > > st/ad_dc/lib/server.conf. > > > > You may need --enable-developer for this to work. > > > > Thanks for using Samba and all the best! > > > > Andrew Bartlett > > > > -- > > Beste Gr??e > > Ghassan Elrayah...

...- 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 := $(patsubst xenstore-%,xenstore_%.o,$(CLIEN...

...: xenstored_%.c $(COMPILE.c) -o $@ $< @@ -66,7 +65,7 @@ clean: testsuite-clean rm -f *.o *.opic *.a - rm -f xen xenstored xs_random xs_stress xs_watch_stress + rm -f xen xenstored xs_random xs_stress rm -f xs_test xenstored_test xs_dom0_test -$(RM) $(PROG_DEP) @@ -86,11 +85,9 @@ $(TESTENV) ./xs_random --fast /tmp/xs_random 100000 $(RANDSEED) $(TESTENV) ./xs_random --fail /tmp/xs_random 10000 $(RANDSEED) -stresstest: xs_stress xs_watch_stress xenstored_test +stresstest: xs_stress xenstored_test rm -rf $(TESTDIR)/store $(TESTDIR)/transactions export $(TESTENV); PID=`./xenstore...

In the hope for some help, I would like some hint on how to diagnose the following single subunit: samba3.blackbox.smbclient_machine_auth.plain In particular the single test samba3.blackbox.smbclient_machine_auth.plain (s4member:local)(s4member:local) Results attached, run is from git at 'origin/v4-10-stable' Thanks in advance (This is because in my full selftest almost all failures

...s/xenstore/Makefile xen-dom0-store/tools/xenstore/Makefile --- xen/tools/xenstore/Makefile 2005-06-16 18:03:27.000000000 +1000 +++ xen-dom0-store/tools/xenstore/Makefile 2005-06-16 14:46:51.000000000 +1000 @@ -82,18 +82,22 @@ stresstest: xs_stress xenstored_test rm -rf $(TESTDIR)/store export $(TESTENV); PID=`./xenstored_test --output-pid`; ./xs_stress 10000; ret=$$?; kill $$PID; exit $$ret +xs_dom0_test: xs_dom0_test.o utils.o + $(LINK.o) $^ $(LOADLIBES) $(LDLIBS) -lxc -o $@ + TAGS: etags `find . -name ''*.[ch]''` tarball: clean cd .. && tar -c -j -v -h -f xenst...

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: