search for: somedirs

On Tue, Apr 25, 2017 at 02:41:58PM +0000, Cook, Malcolm wrote: > Might this combination serve the purpose: > * R session keeps an open handle on the tempdir it creates, > * whatever tempdir harvesting cron job the user has be made sensitive enough not to delete open files (including open directories) Good suggestion but doesn't work with the (increasingly popular)

Hi all. A while ago (April 15th or so) I posted a patch that allows rsync to take multiple --compare-dest or --link-dest arguments, allowing fetching of files not present in multiple trees. I never got any feedback on it, though, so I'm picking it up again. :) Is there any interest in such a patch at all? Below is the usage example i outlined back then; --start-- [...] Its primary usage is

Hi! Usually dovecot auto detects or repairs the size of a maildir message. So I can place a message named "foo" in the cur directory and dovecot uses it. Now I tried the same with a zlib compressed message but here dovecot doesn't recognize/repair the size of the message. When I access this folder via IMAP the connection is diconnected and in dovecot logs I see the following

Hi all, I was busy programming a tool to automatically run some tests to update the FLAC comparison page (http://xiph.org/flac/comparison.html) when I stumbled across some weird behaviour of the flac program. So I compiled from git and it seems that this bug still is there. As I don't have any experience on coding C and don't know which bug-report facility to use, this seemed the

I am attempting to use rsync to copy a large filesystem from an HP-UX server to a Linux server with more than enough filespace. This operation fails. A small directory from the same HP-UX server can be transfered just as expected. The HP-UX server is the source. It has 1Gb RAM - the output of bdf for the volume the source files is on is: Filesystem kbytes used avail %used Mounted

hi, i hope i'm not reporting something well-known; i tried to understand the available bug tracking information. please excuse me if my problem report should not meet your standards, but i want to direct your attention to the following: http://koffein.org/av/rsync-bugreport/ problem report for rsync 2.6.9 on linux/IA32, 09 Dec 2006 Herwig Wittmann

hei everyone, I have a weird problem: if I do a # cd /somedir; stat somesubdir |grep Modify where /somedir is some directory on an SMB-mounted filesystem I get one datetime... but I I do: # cd /somedir; stat * |grep Modify for the same directory I get a Modify time which consistently differs by 1 second. As I'm writing a perl module to detect differences in a filesystem and rely on the

Greetings. If I do this: rsync --hard-links one.server.com::"module/somedir/images/redhat/3.0WS/en/os/i386 module/someotherdir/1.0/images/redhat/3.0WS/en/os/i386" /export/distros I get: /export/distros/i386/... and a conflict between the two sources. I want for destination: /export/distros/images/redhat/3.0WS/en/os/i386 /export/distros/1.0/images/redhat/3.0WS/en/os/i386 In other

Seems like what you really want is an --input-prefix parameter. You might also like a --create-output-directories option. In all cases except absolute paths, the input prefix must be assumed to be the current working directory. Therefore, any relative paths in input file names must be preserved on output to avoid collapsing multiple source directories into a single output directory, with

Do not pass GLOB_MARK as flag for glob(3) in the daemon implementation of glob, so names of directories will not have a trailing slash. This allows users to have filenames that can be used with other tools, such as rm. Add a new test to check this (based on RHBZ#1293271). A mild behaviour change is that users of the glob API now need to append the slash when building paths using its results.

>>>>> <frederik at ofb.net> >>>>> on Tue, 25 Apr 2017 21:13:59 -0700 writes: > On Tue, Apr 25, 2017 at 02:41:58PM +0000, Cook, Malcolm wrote: >> Might this combination serve the purpose: >> * R session keeps an open handle on the tempdir it creates, >> * whatever tempdir harvesting cron job the user has be made

On 26/04/2017 4:21 AM, Martin Maechler wrote: >>>>>> <frederik at ofb.net> >>>>>> on Tue, 25 Apr 2017 21:13:59 -0700 writes: > > > On Tue, Apr 25, 2017 at 02:41:58PM +0000, Cook, Malcolm wrote: > >> Might this combination serve the purpose: > >> * R session keeps an open handle on the tempdir it creates, >

I've done quite a bit of looking, but I haven't found an answer that answers this question. Environment: cygwin on Windows rsync 3.0.4 I know that rsync isn't optimzed for speed on local copies - that's clear in my testing. I'm attemting to sync a large volume of files. (In this case, I'm syncing a rdiff-backup set...) An initial sync will be about one fourth as fast a

I've got a setup where I run nfs over ssh on several distros, and it's been working like a charm on suse, mandrake, redhat 7-9 etc, but I've been unable to get it to work on CentOS. First I set up ssh portforwarding using: /usr/bin/ssh root@<remotehost> -L 250:irc.dynip.no:2049 -f sleep 60d & Then I mount using the following params in fstab: localhost:/somedir

share - xcopy /d /e c:\somedir w:\somedir xcopy /d /e w:\somedir c:\somedir This should have the behavior of making the two directory structures identical, with newer files on one overwriting older or missing files on the other. This only behaves as expected for about half the files. For some files, Windows always wants to re-copy files to the Samba share. I have looked at the files it wants to

Since Ubuntu 20.04 (focal) the rsync option -n (Dry Run) is not working correctly. --- rsync --version rsync? version 3.1.3? protocol version 31 ---- I used this command for about ten years without mayor issues: --- rsync -vaHEiuzn --skip-compress=jpg,JPG,mov,MOV,mp4,MP4,m4v,avi,png --exclude=*.pyc --exclude='somedir/**/.gps.cnf' --exclude='somedir/**/clonezilla' --stats

I've been very interested in these discussions and uses of rsync as a "clone" of Time Machine. A couple of things have been keeping me from a fully automated solution. I'd like to eliminate the need for Samba/NFS mounts of any kind, because they have proven to be unreliable for me and under some operating environments (Cygwin) it breaks --link-dest. In most of the articles

I agree this should be solved in configuration of systemd/tmpreaper/whatever tmp cleaner - the cleanup must be prevented in configuration files of these tools. Moving session directories under /var/run (XDG_RUNTIME_DIR) does not seem like a good solution to me, sooner or later someone might come with auto-cleaning that directory too. It might still be useful if R could sometimes detect when

On 26/04/2017 10:39 AM, Tomas Kalibera wrote: > > I agree this should be solved in configuration of > systemd/tmpreaper/whatever tmp cleaner - the cleanup must be prevented > in configuration files of these tools. Moving session directories under > /var/run (XDG_RUNTIME_DIR) does not seem like a good solution to me, > sooner or later someone might come with auto-cleaning that

Hi, I have been using rsync for many years and never had any kind of problem. Lately I am running out of RAM trying to do an incremental backup to a box that only has 2G of RAM. The entire directory structure I'm mirroring is about 200G of files. A minority of subdirectories have many files. Is there a way to do an incremental backup with --delete option that does not use as much memory? Is