similar to: file.info(path) "inconsistent" with file.exists(path) when path == "C:/"

Hi, Recently I noticed file.copy() would discard the file mode information. Is this the expected behaviour or a bug for file.copy()? > file.create('testfile') [1] TRUE > file.info('testfile') size isdir mode mtime ctime testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39 atime uid gid uname grname

Hi, Recently I noticed file.copy() would discard the file mode information. Is this the expected behaviour or a bug for file.copy()? > file.create('testfile') [1] TRUE > file.info('testfile') size isdir mode mtime ctime testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39 atime uid gid uname grname

Hi, I'm trying to remove/delete a directory usingR. I've tried the following with no success: % Rterm --vanilla > getwd() [1] "C:/Documents and Settings/hb/braju.com.R/aroma.affymetrix/test" > dir.create("foo") > file.info("foo") size isdir mode mtime ctime atime foo 0 TRUE 777 2007-02-28 14:52:10

Hello, The documentation for the tar command leads me to think there is an internal implementation when the command can't be found in the OS. However, it doesn't seem to be the case, as I get an empty .tar file generated on a small example I made : > dir(pattern = "jpg") [1] "MA56237502_635.jpg" > file.info("MA56237502_635.jpg")

Is the following passage from help("file.info"): "Junction points and symbolic links are followed, so information is given about the file/directory to which the link points rather than about the link." correct? Could it be that Windows was not considered? help("file.symlink") mentions several Windows-related issues, but none of those are related to the following.

Hi, I have a writable and readable file on a small network file system (Cisco NSLU2 Unslung; non-NTFS) that I access via a mounted drive on Windows Vista. My problem could be due to a "funny" file system/server, but here it goes: > pathname <- "Q:/foo.txt" > cat(file=pathname, "Hello world!\n") > readLines(pathname) [1] "Hello world!" >

I am using outgoing call files. I typically see the "ooh something changed / timeout" on a regular bases every second to be exact. Then it stops until some other call event happens. So I "mv" my call file to the outgoing spool directory, I am listening to that message, another call file is "mv"'ed into the directory and something happens to the timeout that its

I'm trying to understand why as.Date() is converting a the modified date of a file from August 22 to August 23. > foo <- file.info(file.to.process) > str(foo) 'data.frame': 1 obs. of 10 variables: $ size : num 5.37e+09 $ isdir : logi FALSE $ mode :Class 'octmode' int 436 $ mtime : POSIXct, format: "2010-08-22 23:14:52" $ ctime : POSIXct, format:

Obviously for very large files this is going to be a problem, as well as not being very cache efficient. libext2fs can handle writes to parts of files just fine so copy files in blocks. Also demote the "Permission denied" error to a warning, and add some explanatory text telling people not to use sudo. --- src/ext2fs-c.c | 127 +++++++++++++++++++++++++++++++++++----------------------

I've got a file that's approximately 2.2GB and it seems to be foiling file.info(). When I run `stat' from the shell I get zooey:> stat data.csv File: `data.csv' Size: 2271197563 Blocks: 4440280 IO Block: 4096 regular file Device: 342h/834d Inode: 9994308 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 500/ rpeng) Gid: ( 500/ rpeng) Access:

It looks like I need to elaborate further to get a feedback. I checked the rsync source code and it is using utime() to restore atime file attribute. It is fine to change ctime for that transferred file in this case. What we are having problem is that when rsync gets kicked off and transfers one file to the destination, this action changes ctime of "all" files in the same

Greetings all- I am conducting security testing on a device that uses Linux 2.4 with ext3. I am testing secure overwrite of remnant data in temporary files, but have run into a real good stumpper in the way Ext allocates data blocks. I've got 10 yrs of *NIX behind me, several with Linux, and this has really got me perplexed as I can't find any documentation explaining the subject

hi, the text file that prompts the segfault is 4gb but only 80,937 lines > file.info( "S:/temp/crash.txt") size isdir mode mtime ctime atime exe S:/temp/crash.txt 4078192743 FALSE 666 2017-07-15 17:24:35 2017-07-15 17:19:47 2017-07-15 17:19:47 no On Sun, Jul 16, 2017 at 6:34 AM, Duncan Murdoch <murdoch.duncan at

On Fri, Feb 19, 2016 at 11:12:32AM +0000, Andrei Perietanu wrote: >I'm trying to clone a volume in a storage pool and I'm following the steps >described here: >http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Storage_Pools-Cloning.html > >My code looks like: > > destXML = """ >

This patch adds all the missing commonly used UNIX attributes: st_dev, st_ino, st_nlink, st_rdev, st_blocks, st_blksize, st_ctime. In addition it extends st_atime and st_mtime to 64bits, and adds nanosecond resolution to all three timestamps. This is implemented as an extension to the ATTR message. This patch alone is sufficient for SSHFS to be able to use these attributes. The following two

I have a source file with oxygen-style comments (and description & licence files), and I?m trying to build a package. oxygen & devtools seem to work, and the tarball exists, but install.packages balks. Does anyone know what?s happening? Regards, Jorgen Harmse. > roxygenise(package.dir,clean=TRUE) Setting `RoxygenNote` to "7.3.1" ? roxygen2 requires "Encoding:

Hi, I looked though documentation and also checked last 9 months of archives, but could not find the corresponding information. We are having an issue with incremental backup with arkeia. Arkeia checks if ctime/mtime of the file are changed, if so, it backs up. I realized that when I ran rsync from a cammnd line, it changed ctime, and preserved atime of the file in a destination as

The ext2 filesystem on disk format has two ways to store symlinks. For symlinks >= 60 bytes in length, they are stored as files (so-called "slow symlinks"). For shorter symlinks the symlink is stored in the inode ("fast symlinks"). Previously we only created slow symlinks even if they are shorter than 60 bytes. This didn't matter until recently, when a change went

On Fri, Feb 19, 2016 at 12:33:10PM +0000, Andrei Perietanu wrote: >On Fri, Feb 19, 2016 at 12:12 PM, Martin Kletzander <mkletzan@redhat.com> >wrote: > >> On Fri, Feb 19, 2016 at 11:12:32AM +0000, Andrei Perietanu wrote: >> >>> I'm trying to clone a volume in a storage pool and I'm following the steps >>> described here: >>> >>>

I'm trying to clone a volume in a storage pool and I'm following the steps described here: http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Storage_Pools-Cloning.html My code looks like: destXML = """ <volume>