similar to: log file with unexpected output on deleted files (bug?)

tags 407143 +patch thanks On Fri, 2013-08-16 at 14:42 +0100, Ian Campbell wrote: > tags 688308 +patch > thanks > > A lot of /docs/ is pretty low-level and not all that interesting to be > installed by the packages. However some of it is, and in particular some > is referenced from the manpages. I've cherry-picked the bits which I > think are most interesting in that

tags 688308 +patch thanks A lot of /docs/ is pretty low-level and not all that interesting to be installed by the packages. However some of it is, and in particular some is referenced from the manpages. I've cherry-picked the bits which I think are most interesting in that context. Patch below. 8<--------------- commit 7f8ac283e684b7c713d52ed845cab0704a97abab Author: Ian Campbell <ijc

I have a function: source_dir <- function(path, pattern = "\\.[rR]$", chdir = TRUE) ... documented with ... \usage{source_dir(path, pattern="\\.[rR]$", chdir=TRUE)} ... But I get Codoc mismatches from documentation object 'source_dir': source_dir Code: function(path, pattern = "\\.[rR]$", chdir = TRUE) Docs: function(path, pattern =

On UNIX, I am executing an rsync command, from within a script. The command goes something like this: /usr/bin/rsync --verbose --progress --stats --compress --recursive --times --perms --links --safe-links source_dir/ user at target_machine:/parent_path/source_dir In other words, I am replicating source_dir on a remote machine. It ends up next to a lot of sibling, directories, like this: On

I'm adding a new escape to log-format, %s, to print out the checksum of a file, and I've got a couple problems. They've got to be simple bugs, but I haven't been able to figure them out. The following patch gives me a broken pipe and a bus error when I test it. Note that I've applied the md5 patch beforehand. diff -Naur rsync-2.6.5-md5/log.c rsync-2.6.5/log.c ---

I'm using a little shell script: BUILD_ROOT=/home/llvm-1.7/cfrontend PREFIX="$BUILD_ROOT/install" LOCAL_BUILD_DIR="$BUILD_ROOT/build" SOURCE_DIR="$BUILD_ROOT/src" echo $__me: Building $TARGET echo $__me: BUILD_ROOT == $BUILD_ROOT echo $__me: SOURCE_DIR == $SOURCE_DIR echo $__me: LOCAL_BUILD_DIR == $LOCAL_BUILD_DIR echo $__me: PREFIX == $PREFIX

Hi, Note that one significant change to read.dcf() that happened since R 3.0.2 is the addition of support for arbitrary long lines (commit 63281), which never worked: dcf <- paste(c("aa: ", rep(letters, length.out=10000)), collapse="") writeLines(dcf, "test.dcf") nchar(read.dcf("test.dcf")) # aa # [1,] 8186 The culprit being line

Dear Friends, I've seen this come up on the list in the past, most particularly here. http://groups.google.com/groups?q=rsync+include-from+cat&hl=en&lr=&ie=UT F-8&oe=UTF-8&selm=b2h7t8%2422nt%241%40FreeBSD.csie.NCTU.edu.tw&rnum=2 I find myself in a very similar position. Ideally I'd have a single file, as follows: + /www - /www/bigstuff + /home - /home/tempuser

These assorted patches end up with adding virtio-scsi support to libguestfs. It passes libguestfs-test-tool, but I haven't yet tried to run the full set of tests. In theory > 26 devices can be added, but it's likely that certain parts of the daemon will break if you actually try this. This of course needs to be fixed. Thanks Paolo Bonzini for invaluable help. Rich.

I've been using CMake on my LLVM project for several years now (ever since I abandoned using SCons, and before that, autoconf). During that time I've grown to both love and hate CMake - that is, I love the idea, but hate the language and its limitations. However, due to the recent thread on this list, I realized that I wasn't the only person that felt that way - that there were a lot

Hi All, I am trying to make a customer ISO. When I run this command: mkisofs -o $DESTINATION_FILE -b isolinux/isolinux.bin -c boot.cat \ -no-emul-boot -boot-info-table \ -V "$NAME" -boot-load-size 4 -boot-info-table -R -J -v -T \ -eltorito-alt-boot -e images/efiboot.img \ $DESTINATION_DIR it tells me: Size of boot image is 4 sectors -> No emulation

Hi, Intel Advanced Matrix Extensions (Intel AMX) is a new programming paradigm consisting of two components: a set of 2-dimensional registers (tiles) representing sub-arrays from a larger 2-dimensional memory image, and accelerators able to operate on tiles. Capability of Intel AMX implementation is enumerated by palettes. Two palettes are supported: palette 0 represents the initialized state and

More comprehensive support for virtio-scsi. Passes all the tests. Rich.

May be this is of some interest. I use wine-0.9.43 under ubuntu 6.06 LTS with the linux kernel 2.6.15-28 The MS Train simulator seems to install ok. when trying to start the following messages appear: $ wine launcher.exe -rungame fixme:wave:ALSA_AddCaptureDevice Add support for DSCapture ALSA lib seq_hw.c:456:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory

I have many files (0.4.dat, 0.5.dat, ...) of which I would like to calculate mean value and variance and save the output in a new file where each line shouldlook like: "0.4 mean(0.4.dat) var(0.4.dat)" and so on. Right now I got a a simple script that makes me unhappy: 1. I run it by "R --no-save < script.r > out.dat" unfortunately out.dat has all the original commands in

Here's an update: I checked the ChangeLog for R, and it seems like readDCF was changed in 3.0.2. I went on a whim and copied src/main/dcf.c from R 2.15.3 over to 3.2.2, and R compiled fine and install.packages now work for me. This is probably not ideal, but it at least makes R usable on AIX for me. Would definitely like to help figure out what's wrong with the new dcf.c on AIX.

On Sun, Aug 20, 2017 at 2:47 AM, Ivan A. Kosarev via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hello Daniel, > > >>>> the type of (*x) is not compatible with the type of (*b) or, > >>>> recursively, type of b->i. Similarly, the type of (*b) is > >>>> not compatible with (*x) or, recursively, x->i. > >> ... >

Thank you Kevin. It seems that I misunderstood the purpose of this --delete-missing-args option. If someone has a good suggestion on how to rsync a list of files and delete from the destination any file that is not listed in --files-from, that would be welcome. Thanks, MI -------- Original Message -------- (Kevin Korb via rsync, 2019-04-23 14:11) > --files-from will delete files from

On Sun, Aug 20, 2017 at 8:54 AM, Ivan A. Kosarev via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hello Daniel, > > > The problem with the way you are trying to show this is that > > there are many ways to prove no-alias, and TBAA is one of them. > > The reason i stare at dump files and debug info is precisely to > > separate the TBAA portion from the rest.

Hi everyone, it would be nice if rsync could call an external command to delete files. Than one could call a secure deletion tool like "wipe", which overwrites files a few times before deleting them. Right now Im wiping personal data which I dont need anymore, but it doesnt help much since they can easily be recovered from my backup made with rsync. Bye, Mario -- Der GMX