search for: proctecting

Hi there, Thanks for your time in advance. I am trying to read in multiple files. For example, data.1940 <- read.table("c:/data/1940.csv",header=TRUE,sep=",") data.1950 <- read.table("c:/data/1950.csv",header=TRUE,sep=",") data.1960 <- read.table("c:/data/1960.csv",header=TRUE,sep=",") How can I write a loop to read the

...nd obfuscate the source code running on the web server. I didn''t see yet some solution like this for Rails. Maybe we''ll have something like that on a near future (1 or 2 years)? Is there some plan to make some tool like that, is it possible, or is there a solution already for proctecting the source code of an commercial Rails project? I''d love to use Rails on this, but if there is no way to protect the source code, I''m afraid that somebody will ask me to use PHP. No problem with that, but as I said, I''d love to use Rails there. :-) Thanks! -- Poste...

For my home server i did it like this. Share \\server\backups [backups] path = /media/sambashares/backups read only = No by default everybody had full control on the share. Rights on the folder are 777 In this share/folder i have proctect folders. Like : /media/sambashares/backups/louis /media/sambashares/backups/mywife I created a linux user with the same name as i use in

Hi Louis I'll try your configuration too.. Thanks.  RODRIGO YOSHIOKA Em Terça-feira, 19 de Janeiro de 2016 8:37, L. P. H. van Belle <belle at bazuin.nl> escreveu: For my home server i did it like this. Share \\server\backups [backups]     path = /media/sambashares/backups     read only = No by default everybody had full control on the share. Rights on the folder are 777

...> +/* > + * drm_gem_gpuva_set_lock() - Set the lock protecting accesses to the gpuva list. > + * @obj: the &drm_gem_object > + * @lock: the lock used to protect the gpuva list. The locking primitive > + * must contain a dep_map field. > + * > + * Call this if you're not proctecting access to the gpuva list > + * with the resv lock, otherwise, drm_gem_gpuva_init() takes case > + * of initializing the lock_dep_map for you. > + */ > +#define drm_gem_gpuva_set_lock(obj, lock) \ > + obj->gpuva.lock_dep_map = &(lock)->dep_map > +#define drm_gem_gpuva_ass...

Hi... I'm used to configure samba 3, and now I'm getting some problems using samba 4. My scenario: I have a file server which hosts need to access public folders and private folders.OS: Centos7Samba version: 4.2.3  | 11.el7_2Selinux DisabledFirewalld disabled smb.conf[global]workgroup = WORKGROUP server string = Samba Server %v netbios name = centossecurity = usermap to guest = bad userdns

Enhance the Libvirt_utils module with libvirt connection objects, and read-only and read-writen open functions for them; adapt the rest of the mini-binding to use these objects, instead of opening + closing libvirt connections every time. This has different improvements: a) a libvirt connection is reused for different API calls, improving the communication with remote (input) servers b)

Currently virt-v2v has few custom C-based functions for libvirt operations, which are limited in what they do, and there is a lot of duplicated code. Instead, switch to ocaml-libvirt for all the libvirt interaction currently done by the Libvirt_utils module. This has few advantages: - each input & output module now opens a libvirt connection only once, only when needed - no need to pass

...ct *obj); +#ifdef CONFIG_LOCKDEP +/* + * drm_gem_gpuva_set_lock() - Set the lock protecting accesses to the gpuva list. + * @obj: the &drm_gem_object + * @lock: the lock used to protect the gpuva list. The locking primitive + * must contain a dep_map field. + * + * Call this if you're not proctecting access to the gpuva list + * with the dma-resv lock, otherwise, drm_gem_gpuva_init() takes care + * of initializing lock_dep_map for you. + */ +#define drm_gem_gpuva_set_lock(obj, lock) \ + if (!(obj)->gpuva.lock_dep_map) \ + (obj)->gpuva.lock_dep_map = &(lock)->dep_map +#define drm_g...

...t *obj); +#ifdef CONFIG_LOCKDEP +/** + * drm_gem_gpuva_set_lock() - Set the lock protecting accesses to the gpuva list. + * @obj: the &drm_gem_object + * @lock: the lock used to protect the gpuva list. The locking primitive + * must contain a dep_map field. + * + * Call this if you're not proctecting access to the gpuva list + * with the dma-resv lock, otherwise, drm_gem_gpuva_init() takes care + * of initializing lock_dep_map for you. + */ +#define drm_gem_gpuva_set_lock(obj, lock) \ + if (!(obj)->gpuva.lock_dep_map) \ + (obj)->gpuva.lock_dep_map = &(lock)->dep_map +#define drm_g...

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all