search for: namepac

...> mail -f test at test.org to off@****.com > cat /var/log/dovecot.log : script binary /etc/dovecot/sieve/default.svbin successfully loaded : binary save: not saving binary /etc/dovecot/sieve/default.svbin, because it is already stored : executing script from /etc/dovecot/sieve/default.svbin Namepace : Permission lookup failed from /var/spool/mail/virtual/****.com/****@*****.com/.INBOX.off Namepace : Using permissions from /var/spool/mail/virtual/****.com/*****@*****: mode=0700 gid=-1 Namepace : Permission lookup failed from /var/spool/mail/virtual/*****.com/*****@****.com/.INBOX.off Namepace...

...the environment of base::q, .GlobalEnv, to be loaded as a namespace, causing the error. Giving his replacement q function the environment getNamespace("base") avoids the problem. I can reproduce the problem by making a package that just calls setGeneric("as.hexmode",...) and a NAMEPACE file with exportMethods("as.hexmode"). If my .Rprofile puts a version of as.hexmode with environment .GlobalEnv into the base namespace, then I get the same error when trying to load the package. I suppose this is mostly a curiosity and unlikely to happen to most people but it did conf...

...ace, causing the error. >> Giving his replacement q function the environment getNamespace("base") >> avoids the problem. >> >> I can reproduce the problem by making a package that just calls >> setGeneric("as.hexmode",...) and a NAMEPACE file with >> exportMethods("as.hexmode"). If my .Rprofile puts a version of as.hexmode >> with environment .GlobalEnv into the base namespace, then I get the same >> error when trying to load the package. >> >> I suppose this is mostly...

...::q, .GlobalEnv, to be loaded as a namespace, causing the error. > Giving his replacement q function the environment getNamespace("base") > avoids the problem. > > I can reproduce the problem by making a package that just calls > setGeneric("as.hexmode",...) and a NAMEPACE file with > exportMethods("as.hexmode"). If my .Rprofile puts a version of as.hexmode > with environment .GlobalEnv into the base namespace, then I get the same > error when trying to load the package. > > I suppose this is mostly a curiosity and unlikely to happen to mos...

I have a package that I'm developing that I need to unload the library. Long story short I figured out that the leaving the compiled code loaded lead to a segmentation fault, but unloading the code will fix it. I've read the documentation and it appears that there are several ways to do this? What is the popper accepted current standard for unloading compiled code? The options as I

...>> Giving his replacement q function the environment > getNamespace("base") > >> avoids the problem. > >> > >> I can reproduce the problem by making a package that just calls > >> setGeneric("as.hexmode",...) and a NAMEPACE file with > >> exportMethods("as.hexmode"). If my .Rprofile puts a version of > as.hexmode > >> with environment .GlobalEnv into the base namespace, then I get the > same > >> error when trying to load the package. > >> >...

Hi Folks, Using libvirt python bindings we are creating an lxc container.Here is the problem that we see sometimes (say 20 % of the time) when we create a new container. 1.container gets created, and also starts.However the we are not able to enter the namepace of the container.It throws an error initPid not available.We see that the using netstat command , socket connection is closed. 2.To get around this problem we have to stop and start the container again.We see that socket under (/var/run/libvirt/*) connection is established and we are able to ent...