search for: sanitarium

I have the following script that I am working on #!/bin/bash date=$(date +%F--%T) #ssh parameters user=aquj001 remotehost=qa4app localdir=/home/aquj001/INFENG/scripts remotedir=/home/aquj001/recievingDir.$date linkdest=$(ssh $user@$remotehost /usr/linux/bin/readlink/ /home/aquj001/recievingDir.current) rsync -a --compress --link-dest=$linkdest --out-format='%i %n%L %l %M'

On Tue, Mar 20, 2018 at 5:49 PM Kevin Korb <kmk at sanitarium.net> wrote: > Nothing there should be preventing incremental indexing. That means it > should start copying as soon as it finds a file that needs to be copied. > Doesn't it tries to create all (empty) directories first? > On 03/20/2018 02:33 PM, Bráulio Bhavamitra wrote: >...

...s the directories as it needs them. If you want to watch it looking through files it doesn't need to copy you can add -ii (see --itemize-changes for what the output means). On 03/20/2018 05:24 PM, Bráulio Bhavamitra wrote: > > > On Tue, Mar 20, 2018 at 5:49 PM Kevin Korb <kmk at sanitarium.net > <mailto:kmk at sanitarium.net>> wrote: > > Nothing there should be preventing incremental indexing.  That means it > should start copying as soon as it finds a file that needs to be copied. > > Doesn't it tries to create all (empty) directories first? ...

...ng, so the target must not be storing them, which I have no idea why. The directory I’m writing to is 777. What is the flag to tell rsync to ignore the timestamps? Thanks, Blake On 6/2/16, 6:18 PM, "rsync on behalf of Kevin Korb" <rsync-bounces at lists.samba.org on behalf of kmk at sanitarium.net> wrote: >It is saying the timestamp is wrong and that it is copying the file and >changing the timestamp. If it does that every time then either the >timestamps are changing on the source or the target isn't storing them. > >On 06/02/2016 06:13 PM, McDowell, Blake wrote:...

...delete options. On 03/27/2015 09:31 AM, Aron Rotteveel wrote: > I am now running with --delete --numeric-ids --relative but the > problem still persists. > > -- Best regards / Met vriendelijke groet, > > Aron Rotteveel > > 2015-03-27 14:22 GMT+01:00 Kevin Korb <kmk at sanitarium.net > <mailto:kmk at sanitarium.net>>: > > Try also removing --delete-excluded. Without those two options > there should be no reason for rsync to require gigs of RAM. Well, > unless the other system has rsync 2.x. > > On 03/27/2015 07:29 AM, Aron Rotteveel wrote:...

...nc won't touch the file unless _some_ relevant change is observed? It just concerned me because the file list was extensive, and I definitely don't want anything copied unless for example the checksums don't match. Thanks, -Clint On Wed, Oct 28, 2015 at 5:41 AM, Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > - --checksum generally takes a lot longer than --size-only. A delta > transfer generally goes quicker than a checksum. However, if you want > to make a list of what is corrupt a checksumming utility that is le...

I have worked in IT for several years and programming or anything related to this is not exactly one of my strengths. I need help creating a vesamenu.. Im trying to setup up so I can access my Acronis backup and disaster recovery 10 server, knoppix live cd, hardware diagnostics - pcdoctor and maybe a hiren type boot cd. I checked the Linux irc channel which I guess is now abandoned. If anyone

...#39;`^`'~*-,._.,-*~'`^`'~*-,._., > Kevin Korb Phone: (407) 252-6853 > Systems Administrator Internet: > FutureQuest, Inc. Kevin at FutureQuest.net (work) > Orlando, Florida kmk at sanitarium.net (personal) > Web page: http://www.sanitarium.net/ > PGP public key available on web site. > ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., > > -- > Please use reply-all for most rep...

...1__1199_Workprint__UHD_DPX/119 >9WP_00086405.dpx >f..t....... >2012_79_1_14_1__1199_Workprint/2012_79_1_14_1__1199_Workprint__UHD_DPX/119 >9WP_00086406.dpx ~Blake On 6/2/16, 5:44 PM, "rsync on behalf of Kevin Korb" <rsync-bounces at lists.samba.org on behalf of kmk at sanitarium.net> wrote: >Instead of the second -v (or even the first) add --itemize-changes. It >will tell you why each file is being copied. If the file timestamps are >not correct then perhaps the underlying storage doesn't allow arbitrary >mtime changes. > >On 06/02/2016 05:23 PM...

...or linear tape but give the choice > between cp (which is faster and causes less problems but offers almost > zero verbosity) and rsync, I’ll choose rsync. If people know of other > options, I’d be very happy to know of them. > > On 6/2/16, 6:33 PM, "Kevin Korb" <kmk at sanitarium.net> wrote: > >> The man page has a section on what all the itemize-changes flags do. >> >> There is a --ignore-times but the result is what you have now, re-copy >> everything even if the timestamp matches. >> >> The best you can really do with storage th...

...e rsync is not the best for linear tape but give the choice between cp (which is faster and causes less problems but offers almost zero verbosity) and rsync, I’ll choose rsync. If people know of other options, I’d be very happy to know of them. On 6/2/16, 6:33 PM, "Kevin Korb" <kmk at sanitarium.net> wrote: >The man page has a section on what all the itemize-changes flags do. > >There is a --ignore-times but the result is what you have now, re-copy >everything even if the timestamp matches. > >The best you can really do with storage that can't handle timestamps is...

In message <560C79FF.5010302 at sanitarium.net>, Kevin Korb <kmk at sanitarium.net> wrote: >Because you are making two/one. Change to: >rsync -n -v --itemize-changes -checksum -a one/ two/ OK, I tried it with your suggested command line, and yes, that produces rather more substantially useful results. However... Perhaps...

...`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone: (407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. Kevin at FutureQuest.net (work) Orlando, Florida kmk at sanitarium.net (personal) Web page: http://www.sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,

...k-dest and they all tried to transfer all files --link-dest=../backup-2016-02-01-0100 --link-dest=backup-2016-02-01-0100 --link-dest=/backup-2016-02-01-0100 --link-dest=/backup/backup-2016-02-01-0100 --link-dest=./backup/backup-2016-02-01-0100 On Mon, Feb 8, 2016 at 5:01 PM Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > try: --link-dest=../backup-2016-02-01-0100 > > On 02/08/2016 04:51 PM, Sam Holton wrote: > > Thanks for the reply. The link-dest is different. It is Feb 1 while > > the source is Feb 2. > > &gt...

...Well, unless the other system has rsync 2.x. On 03/27/2015 07:29 AM, Aron Rotteveel wrote: > Yes, I removed "--no-inc-recursive", without success. > > -- Best regards / Met vriendelijke groet, > > Aron Rotteveel > > 2015-03-27 12:24 GMT+01:00 Kevin Korb <kmk at sanitarium.net > <mailto:kmk at sanitarium.net>>: > > Have you tried removing --no-inc-recursive yet? > > On 03/27/2015 07:19 AM, Aron Rotteveel wrote: >> Hi Roland, > >> Thanks for the reply. Memory usage on both machines seem fine. >> The server has 4GB's...

...three (link-dest, source, target) are directories but get the same result. The directory backup-2016-02-02-0100 is created on the target server and all files start to be transferred to it. Must be an issue with the way I'm setting link-dest On Mon, Feb 8, 2016 at 4:42 PM Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > by misaligned I meant that your source is a directory, your link-dest > is a directory (with the same name even), and your target is the root > of the share. All 3 params should be directories and the link-dest...

Hi people, I've got some problems on running the game Sanitarium on Wine: the game crashes when entering the second level (after it is loaded) and pops up the following error message: "Unable to create graphic (you may be out of swap file space) The game will be terminated." When I clik the button Ok, other error message pops up: "Runtime Error...

On Sat Jan 10 2015 at 5:21:33 AM Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > What does --itemize-changes say about that file? Try using the stat > command on the various copies of it to see what is different about them. > In my original message, I stated I used --itemize-changes, and I...

...gt; which I have no idea why. The directory I’m writing to is 777. > > What is the flag to tell rsync to ignore the timestamps? > > Thanks, > Blake > > On 6/2/16, 6:18 PM, "rsync on behalf of Kevin Korb" > <rsync-bounces at lists.samba.org on behalf of kmk at sanitarium.net> wrote: > >> It is saying the timestamp is wrong and that it is copying the file and >> changing the timestamp. If it does that every time then either the >> timestamps are changing on the source or the target isn't storing them. >> >> On 06/02/2016 06:...

What about -c? It seems I'm getting a lot of spurious file transfer candidates when using: -avvznIi --no-o --no-g --no-p It's showing transfers (receive) for many files I know haven't been tampered with. Thanks, -Clint On Tue, Oct 27, 2015 at 7:53 PM, Kevin Korb <kmk at sanitarium.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > That is correct. Rsync will re-copy (delta xfer unless --wholefile) > all the files. You can always --dry-run if you aren't sure. > > On 10/27/2015 10:07 PM, Clint Olsen wrote: > > Hi: > > &...