search for: tempf

...ntation of R-dev and R-3.4.3, under ?gsub > replacement > ... For perl = TRUE only, it can also contain "\U" or "\L" to convert the rest of the replacement to upper or lower case and "\E" to end case conversion. However, the following code runs differently: tempf <- tempfile() writeLines(enc2utf8("author: Am?lie"), con = tempf, useBytes = TRUE) entry <- readLines(tempf, encoding = "UTF-8") gsub("(\\w)", "\\U\\1", entry, perl = TRUE) "AUTHOR: AM?LIE" # R-3.4.3 "A"...

...| > | > replacement > | > ... For perl = TRUE only, it can also contain "\U" or "\L" to convert the rest of the replacement to upper or lower case and "\E" to end case conversion. > | > | However, the following code runs differently: > | > | tempf <- tempfile() > | writeLines(enc2utf8("author: Am?lie"), con = tempf, useBytes = TRUE) > | entry <- readLines(tempf, encoding = "UTF-8") > | gsub("(\\w)", "\\U\\1", entry, perl = TRUE) > | > | > | "AUTHOR: AM?LIE" # R-3.4.3...

...; | > ... For perl = TRUE only, it can also contain "\U" or "\L" to > convert the rest of the replacement to upper or lower case and "\E" to end > case conversion. > > | > > | However, the following code runs differently: > > | > > | tempf <- tempfile() > > | writeLines(enc2utf8("author: Am?lie"), con = tempf, useBytes = TRUE) > > | entry <- readLines(tempf, encoding = "UTF-8") > > | gsub("(\\w)", "\\U\\1", entry, perl = TRUE) > > | > > | > > | "AU...

...g about 200GB of data from Windows to UNIX, I have setup Cygwin/rsync on Windows 2003R2 and when rsync was run on Windows it copied about 40GB of data and after that it is failing with the following errors: *** Skipping any contents from this failed directory *** rsync: recv_generator: mkdir "/tempfs/0000238c/80/12/59" failed: Permission deni ed (13) *** Skipping any contents from this failed directory *** rsync: recv_generator: mkdir "/tempfs/0000238c/80/12/5a" failed: Permission deni ed (13) *** Skipping any contents from this failed directory *** rsync: recv_generator: mkdir...

...ame. in a sense, the lexical scoping rule is first applied to acquire a value, and this value is then applied to the new local variable, and is then immediately changed by the assignment operation. i only noticed this when assigning variables to entries within a 'list' structure, like so: tempf <- function(x, local = TRUE) { executing_environment <- environment() closure_environment <- parent.env(executing_environment) print(executing_environment) cat(str(mget("my_list", envir = executing_environment, inherits = FALSE, ifnotfound = NA)[[1]])) prin...

...ion on my hard drive. I can boot to it with Grub no problem. I've added the ioslinux directory with isolinux.bin, isolinux.cfg, a kernel (with initrd, loopback, iso support), and an initrd file. My next mission is to some how make it a bootable CD distro with certain directories mounted on a tempfs so some files can be writable. It would also be nice to try and auto detect the network card. I've been doing research for the last couple days and I'm pretty much stuck. Any help at all would be greatly appreciated. -- Matt http://www.playway.net ----

Hi, i try to create a openWRT Samba 4.3 package and stumbled across the fact that samba 4.3 will create those message socks inside the private-dir. That results in creating entries inside /etc/samba/msg.sock. On openWRT /var is a tempFS in ram, so anything there is not a problem regarding nvram and wear leveling. Yet the root uses a jffs2 overlay. So while those message socks have no size, jffs2 still needs to write the dir table, since they survive a reboot. I'm now wondering how frequently those sock entries are created/de...

Hi all, Does any one know of any encryption/decryption algorithms in R? I'm not looking for anything robust - I want some way of printing output to the screen that the user can't read immediately, but can decrypt a little later. The main thing I don't want to the user to see is a number, so (e.g.) ROT13 isn't appropriate. Hadley -- Assistant Professor / Dobelman Family Junior

...11/03/16 12:08, Andy Walsh wrote: > Hi, > > i try to create a openWRT Samba 4.3 package and stumbled across the fact > that samba 4.3 will create those message socks inside the private-dir. That > results in creating entries inside /etc/samba/msg.sock. > > On openWRT /var is a tempFS in ram, so anything there is not a problem > regarding nvram and wear leveling. Yet the root uses a jffs2 overlay. So > while those message socks have no size, jffs2 still needs to write the dir > table, since they survive a reboot. > > I'm now wondering how frequently those soc...

...ound the same issue reported at <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666135>. For comparison I just installed a fresh Debian Wheezy rc1 and noticed that the XenStore tdb there is locates in /var/_run_/xenstore/tdb instead of /var/_lib_/xenstore/tdb. Since /var/run/ lives on a tempfs, it's nuked on every reboot and thus the problem doesn't exist there. Is the XenStore tdb supposed to survive a reboot or must it be cleared between each reboot? Sincerely Philipp -- Philipp Hahn Open Source Software Engineer hahn at univention.de Univention GmbH...

...ound the same issue reported at <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666135>. For comparison I just installed a fresh Debian Wheezy rc1 and noticed that the XenStore tdb there is locates in /var/_run_/xenstore/tdb instead of /var/_lib_/xenstore/tdb. Since /var/run/ lives on a tempfs, it's nuked on every reboot and thus the problem doesn't exist there. Is the XenStore tdb supposed to survive a reboot or must it be cleared between each reboot? Sincerely Philipp -- Philipp Hahn Open Source Software Engineer hahn at univention.de Univention GmbH...

...> > Hi, > > > > i try to create a openWRT Samba 4.3 package and stumbled across the fact > > that samba 4.3 will create those message socks inside the private-dir. That > > results in creating entries inside /etc/samba/msg.sock. > > > > On openWRT /var is a tempFS in ram, so anything there is not a problem > > regarding nvram and wear leveling. Yet the root uses a jffs2 overlay. So > > while those message socks have no size, jffs2 still needs to write the dir > > table, since they survive a reboot. > > > > I'm now wondering...

Hello everyone. I'm wondering what other people's experiences are WRT systems becoming unresponsive (unable to ssh in, etc) for brief periods of time when a large amount of IO is being performed. It's really starting to cause a problem for us. We're on Dell PowerEdge 1955 blades - but this same issue has caused us problems on PE1950, PE1850, PE1750 servers. We're running

Hi Some developers here said a long time ago that someone should show the code for LZO compression support for ZFS before talking about the next step. I made that code with a friend and we also made a little benchmark to give a first impression: http://denisy.dyndns.org/lzo_vs_lzjb/ I hope we made no technical error, but if you find something not accurate, we will correct it. Denis -- This

Hello All, I am at the switch from sssd to winbind based samba domain members (Debian 9 stretch). I am using Samba 4.10.2 packages from Louis ( http://apt.van-belle.nl/ ) and rid backend for idmap. *My problem:* I am able to logon to my domain members using winbind_pam as long as my client is connected to a network where a domain controller is reachable. As soon as I shutdown and connect a

...+bug/1165461 There the error was tracked down to /var/run/samba/gencache.tdb being stored on a temporary file system and due to this being deleted with every restart. I was able to find that "gencache.tdb" on my Debian 9 systems is stored at /run/samba/gencache.tdb being "run" a tempfs, too. In the bug report it is described that after changing/adding a new setting "lock directory = /var/cache/samba/" in smb.conf everything worked again as expected. So I did the same and voila ...caching is working even after restarts. Never the less I am still not sure if this is a c...

...he error was tracked down to /var/run/samba/gencache.tdb being > stored on a temporary file system and due to this being deleted with > every restart. > I was able to find that "gencache.tdb" on my Debian 9 systems is > stored at /run/samba/gencache.tdb being "run" a tempfs, too. > In the bug report it is described that after changing/adding a new > setting "lock directory = /var/cache/samba/" in smb.conf everything > worked again as expected. > So I did the same and voila ...caching is working even after restarts. I haven't upgraded to 4.1...

...down to /var/run/samba/gencache.tdb being > > stored on a temporary file system and due to this being deleted with > > every restart. > > I was able to find that "gencache.tdb" on my Debian 9 systems is > > stored at /run/samba/gencache.tdb being "run" a tempfs, too. > > In the bug report it is described that after changing/adding a new > > setting "lock directory = /var/cache/samba/" in smb.conf everything > > worked again as expected. > > So I did the same and voila ...caching is working even after restarts. > >...