search for: ddp

Hello all, I am not sure my original mail got through to the list (I haven''t received it back), so I attach it below. Anyhow, now I have a saved kernel crash dump of the system panicking when it tries to - I believe - deferred-release the corrupted deduped blocks which are no longer referenced by the userdata/blockpointer tree. As I previously wrote in my thread on unfixeable

...e allowed"=true > > service samba-ad-dc start > > Then try to add your OU ldif again. > > Rowland > Got nice results, later I moved to other migrations and that's the only error I don't know how to solve: Error: Unable to parse dn 'CN=echo+ipServiceProtocol=ddp,CN=services,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=ldom' dn: CN=echo+ipServiceProtocol=ddp,CN=services,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=ldom cn: echo objectClass: ipService objectClass: top ipServicePort: 4 ipServiceProtocol: ddp -------------- next part ------...

Version 1.4 of package "g.data" is available on CRAN. This upgrade is necessary for it to work under R-1.8.0, and is fully backward compatible. Description: Create and maintain delayed-data packages (DDP's). Data stored in a DDP are available on demand, but do not take up memory until requested. You attach a DDP with g.data.attach(), then read from it and assign to it in a manner similar to S-Plus, except that you must run g.data.save() to actually commit to disk. Thanks very much to...

Version 1.4 of package "g.data" is available on CRAN. This upgrade is necessary for it to work under R-1.8.0, and is fully backward compatible. Description: Create and maintain delayed-data packages (DDP's). Data stored in a DDP are available on demand, but do not take up memory until requested. You attach a DDP with g.data.attach(), then read from it and assign to it in a manner similar to S-Plus, except that you must run g.data.save() to actually commit to disk. Thanks very much to...

...>> > >> Then try to add your OU ldif again. > >> > >> Rowland > >> > > Got nice results, later I moved to other migrations and that's the only error I don't know how to solve: > > Error: Unable to parse dn 'CN=echo+ipServiceProtocol=ddp,CN=services,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=ldom' > > > > dn: CN=echo+ipServiceProtocol=ddp,CN=services,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=ldom > > cn: echo > > objectClass: ipService > > objectClass: top > > ipServicePort...

Version 1.6 of the "g.data" package is available on CRAN. The "g.data" package is used to create and maintain delayed-data packages (DDP's). Data stored in a DDP are available on demand, but do not take up memory until requested. You attach a DDP with g.data.attach(), then read from it and assign to it in a manner similar to S-Plus, except that you must run g.data.save() to actually commit to disk. This new version uses delayedA...

Version 1.6 of the "g.data" package is available on CRAN. The "g.data" package is used to create and maintain delayed-data packages (DDP's). Data stored in a DDP are available on demand, but do not take up memory until requested. You attach a DDP with g.data.attach(), then read from it and assign to it in a manner similar to S-Plus, except that you must run g.data.save() to actually commit to disk. This new version uses delayedA...

A new package "g.data" is available on CRAN, to create and maintain databases that work more like the S-Plus model. Here's the official Description for g.data (v1.2): Create and maintain delayed-data packages (DDP's). Data stored in a DDP are available on demand, but do not take up memory until requested. You attach a DDP with g.data.attach(), then read from it and assign to it in a manner similar to S-Plus, except that you must run g.data.save() to actually commit to disk. Here's a very ab...

A new package "g.data" is available on CRAN, to create and maintain databases that work more like the S-Plus model. Here's the official Description for g.data (v1.2): Create and maintain delayed-data packages (DDP's). Data stored in a DDP are available on demand, but do not take up memory until requested. You attach a DDP with g.data.attach(), then read from it and assign to it in a manner similar to S-Plus, except that you must run g.data.save() to actually commit to disk. Here's a very ab...

...> service samba-ad-dc start >> >> Then try to add your OU ldif again. >> >> Rowland >> > Got nice results, later I moved to other migrations and that's the only error I don't know how to solve: > Error: Unable to parse dn 'CN=echo+ipServiceProtocol=ddp,CN=services,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=ldom' > > dn: CN=echo+ipServiceProtocol=ddp,CN=services,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=ldom > cn: echo > objectClass: ipService > objectClass: top > ipServicePort: 4 > ipServiceProtocol: dd...

...>> Then try to add your OU ldif again. >>>> >>>> Rowland >>>> >>> Got nice results, later I moved to other migrations and that's the only error I don't know how to solve: >>> Error: Unable to parse dn 'CN=echo+ipServiceProtocol=ddp,CN=services,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=ldom' >>> >>> dn: CN=echo+ipServiceProtocol=ddp,CN=services,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=ldom >>> cn: echo >>> objectClass: ipService >>> objectClass: top >>...

Dear all, I have build a Domain with to samba4 DC's. Everything works fine DNS Replication, User Replication, etc. Now I started to create a Logonscript. I doesn't reach to get the Logonscript automatcally loaded. The client doesn't load the DDP, doesn't load the GPO and doesn't load the logonscript individually in the user-setup by Remote Server Tools. When I start \\DC1\netlogon\user.bat manually, everything works fine. I'm working now about 12 month with Samba4, have set up a couple of maschines, but every time I stuck wit...

...like two files have exactly the same name, but actually they're different: one as "é" encoded as 0xCC81, and the other one (the "good one") as 0xC3A9. Of course similar problems occur for all accented letters. So here's the setup: I have a very weird proprietary system (DDP server), probably running internally some ancient version of Samba. People copied these files to this old server from Mac workstations. So far so good. I have a new server, running CentOS 7.3 and Samba 4.6. I mounted the CIFS exports from the DDP server : # mount | grep temp //192.168.5.150/w-ru...

...your OU ldif again. > >>>> > >>>> Rowland > >>>> > >>> Got nice results, later I moved to other migrations and that's the only error I don't know how to solve: > >>> Error: Unable to parse dn 'CN=echo+ipServiceProtocol=ddp,CN=services,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=ldom' > >>> > >>> dn: CN=echo+ipServiceProtocol=ddp,CN=services,CN=ypServ30,CN=RpcServices,CN=System,DC=mydomain,DC=ldom > >>> cn: echo > >>> objectClass: ipService > >>>...

Sun, 26 Jul 2020 12:06:03 +0100 Rowland penny via samba <samba at lists.samba.org>: > On 26/07/2020 10:58, RhineDevil wrote: > > You said you didn't want to help me about this but if you'd do at least I'd learn something useful for custom schemas, since this type of error isn't referenced anywhere > > No, I said I wouldn't help you shoot yourself in the

I am new on R, so I have a maybe naive question: if I have many large data.frames and I use only one or two per session, what's the best way? If all are stored in the actual .Rdata, the system gets slow. On the other hand, I wouldn't like to make a separate package for the data. Should I save it with save() and then remove it with rm() ? Could I reload it then? Thanks for suggestions

I insert an function call in the IR, and causes the following error. and the error seems to happen on some cases. The attached file nest.c can be processes successfully and the nest-ddp.ll is the output file, but the nr__routines.c will fail. llvm-3.2-svn/lib/VMCore/DebugLoc.cpp:60: void llvm::DebugLoc::getScopeAndInlinedAt(llvm::MDNode*&, llvm::MDNode*&, const llvm::LLVMContext&) const: Assertion `unsigned(ScopeIdx) <= Ctx.pImpl->ScopeRecords.size() &&...

...#39;re different: one as "é" encoded as 0xCC81, and the other one (the > "good one") as 0xC3A9. Of course similar problems occur for all accented > letters. 0xC3A9 is utf-8 of é, so that's correct. > So here's the setup: I have a very weird proprietary system (DDP > server), probably running internally some ancient version of Samba. > People copied these files to this old server from Mac workstations. So > far so good. > > I have a new server, running CentOS 7.3 and Samba 4.6. I mounted the > CIFS exports from the DDP server : > > #...

I have a daily job that attaches hundreds of pseudo-packages containing data as promise objects (DDP's, ref: g.data package), and plots the results to a multi-page pdf device. Sometimes it fails. Under R-2.2.1 it just gave segfaults. Under R-2.3.1 it gave this error message: *** caught segfault *** address (nil), cause 'memory not mapped' Traceback: 1: load(system.file(&q...

...ter installing 2.6.18-53.1.4el kernel, I'm having a bit of a struggle... # make -C /lib/modules/2.6.18-53.1.4.el5/build \ SUBDIRS=/usr/src/appletalk modules make: Entering directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686' CC [M] /usr/src/appletalk/aarp.o CC [M] /usr/src/appletalk/ddp.o CC [M] /usr/src/appletalk/dev.o CC [M] /usr/src/appletalk/atalk_proc.o CC [M] /usr/src/appletalk/sysctl_net_atalk.o LD [M] /usr/src/appletalk/appletalk.o Building modules, stage 2. MODPOST CC /usr/src/appletalk/appletalk.mod.o LD [M] /usr/src/appletalk/appletalk.ko make:...