On Tue 08 Apr 2025, Graham Leggett via rsync wrote:
>
> I have a backup that was created with --fake-super that I need to restore to
> a fresh partition on the same machine as the backup (source and destination
> on the same machine).
>
> The docs describe how --fake-super is used to make the b
On Sat 11 Jan 2025, Anthony LaTorre via rsync wrote:
> Thanks for your quick response. The rsyncd.conf file looks like:
>
> charset = utf-8
> [user]
> path = /c/user
> comment = ""
> use chroot = true
Note the chroot... So "/" equals /c/user
> uid = root
> gid = root
> read only = f
On Mon 23 Dec 2024, Mario Marietto via rsync wrote:
>
> Everytime I try to copy a file from one USB disk to another one (does not
> matter which one),I get this kind of error :
>
>
> mario@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync
> -avxHAXP FreeBSD-141-UFS-sdc-DarkMatter.
On Wed 16 Oct 2024, Chris Green via rsync wrote:
>
> I use it almost exclusively on Linux systems and it would be really
> handy if I could set a number of options which would always be used
> when I run rsync. These would be in addition to -a which is useful
> but not quite enough.
>
> In parti
On Wed 09 Oct 2024, McDowell, Blake via rsync wrote:
> Linux servers one running TrueNAS-13.0-U6 and the other running
> TrueNAS-13.0-U3.1.
>
> I connect to both on a Mac via smb over fiber.
>
> Using cp -a also updates the timestamp of the copied file to today and does
> not back-date it to t
On Sun 02 Jun 2024, Chris Green via rsync wrote:
> I have an rsync daemon running on a 64-bit (x86_64) system which I
> successfully use for backups from several other 64-bit systems on my
> LAN.
>
> I want to use it for backups from a BeagleBone Black (32-bit, armv7l)
> but it fails as follows:-
On Mon 03 Jun 2024, Kevin Korb via rsync wrote:
> It appears that xattr changes (that is what the x mens) never made it into
> the verbose output. I would call that a bug but I would rather it be fixed
> by making -v include -i.
I think -v only shows when file data is transferred (or files /
dir
On Wed 15 May 2024, Graham Leggett via rsync wrote:
>
> Then we check the disk underneath rsync:
>
> [root@arnie images]# dd if=/dev/urandom of=random.img count=1024 bs=10M
> status=progress
> 1604321280 bytes (1.6 GB, 1.5 GiB) copied, 16 s, 100 MB/s^C
> 159+0 records in
> 159+0 records out
> 16
On Thu 18 Jan 2024, Roger Price via rsync wrote:
> I am backing up a user's directories from local machine titan to remote
> machine maria. On the remote machine maria file /etc/rsyncd.conf contains
>
> [rprice-home]
> ...
> exclude = *.dvi
>
> I start the backup by using this command on the
On Fri 22 Sep 2023, Kevin Korb via rsync wrote:
> 444 {} +' to make read only files for rsync to want to chmod, then used cp
> -al to make several duplicate trees using hard linked files. An rm -rf on
> one such tree took .97 seconds while an rsync deletion took 1.25 seconds.
Be sure to drop the
On Sun 03 Sep 2023, Perry Hutchison via rsync wrote:
> On the source system:
>
> $ rsync --version
> rsync version 2.6.8 protocol version 29
> On the destination system:
> $ rsync --version
> rsync version 3.0.7 protocol version 30
The current version is 3.2.7, especially 2.6.8 is quite an
On Sat 03 Jun 2023, Maurice R Volaski via rsync wrote:
> I have an rsync script that it is copying one computer (over ssh) to a shared
> CIFS mount on Gentoo Linux, kernel 6.3.4. The script runs for a while and
> then at some point quits knocking my ssh session offline on all terminals and
> it
On Mon 14 Nov 2022, Wes Render via rsync wrote:
> Hello, I'm running an rsync like this:
>
> rsync -avSHP --delete-after
> --log-file=/opt/mirrorsync/centos_mirror/rsync-1.log
> --exclude-from=/opt/mirrorsync/centos_mirror/excludelist.txt
> rsync://centos.mirror.rafal.ca/CentOS/ /data/centos
>
On Sat 17 Sep 2022, Colton Lewis via rsync wrote:
> This is on a system where /etc/rsyncd.conf does not exist and goes away if
> /etc/rsyncd.conf is an empty file.
>
> Version: rsync version 3.2.5 protocol version 31
> Command: rsync --daemon
> What happens: The program outputs "Failed to pars
On Tue 12 Jul 2022, Kevin Korb via rsync wrote:
> Rsync does not verify writes. --checksum doesn't verify anything. Sounds
> like you want a file verification tool. The simplest would be md5sum.
Running rsync --checksum directly after transferring your files will
verify that the files are writt
On Fri 24 Jun 2022, Kevin Korb via rsync wrote:
> Nope. Rsync groups are not groups of users they are just @users with their
> own password. I believe the @ just designates that you intend multiple
> people to have that password and use that username.
I think I have to disagree here.
The manpa
On Mon 07 Feb 2022, Edwardo Garcia via rsync wrote:
>
> Lets call module mirror
> this results in about 200 or more directories (projects), but I only want
> one of them, lets call it foo, the problem is foo/ has about 50
> directories, but the one and only one we want is bar, but bar also has
>
On Thu 03 Feb 2022, Andy Smith via rsync wrote:
> sudo rsync -iPva \
> --inplace \
> --numeric-ids \
> --delete \
> /data/backup/rsnapshot/daily.0/cacti/ \
> root@koff:/data/backup/rsnapshot/daily.0/cacti/
>
> ...
>5,258 100%5.78kB/s0:00:00 (xfr#1276, to-ch
On Mon 24 Jan 2022, Jürgen Bausa via rsync wrote:
>
> However, that's just a proposal. But the behavior of trailing spaces is
> something I guess should be corrected.
Is it?
How would you otherwise specify a space that you *do* intend to be
relevant?
Paul
--
Please use reply-all for most rep
On Tue 03 Aug 2021, Chris Green via rsync wrote:
> Is there a way to copy (for example) the /etc hierarchy from one
> system to another preserving root ownership of files and without
> revealing root passwords all over the place?
Best way is to run an rsync daemon on the source system, and be sur
On Fri 26 Mar 2021, Harry Mangalam via rsync wrote:
>
> I'm trying to improve a parallel rsync wrapper called parsyncfp (pfp) in
> response to a user request. He wants rsync to emit data on multiple
> interfaces (one interface per rsync instance). From the man page it seems
> like the '--address
On Thu 18 Feb 2021, Bri Hatch via rsync wrote:
>
> We use authprogs for more than just rsync though, and want more granularity
> than rrsync can support. If you force rrsync for the ssh key via
> command="rrsync" then that key may only be used to run rsync, you can't
> also allow additional comman
On Thu 10 Dec 2020, Chris Green via rsync wrote:
>
> Occasionally, because I've moved things around or because I've done
> something else that breaks things, the hard links aren't created as
> they should be and I get a very space consuming backup increment.
>
> Is there any easy way that one can
On Mon 03 Aug 2020, Matt Stevens via rsync wrote:
> So I've gotten excluding paths to work as a standalone command. When I paste
> this into a script however, it ignores the exclusions. Any advice?
>
> rsync -aXvr --times --links
> --exclude={'*.vdi','*.vmdk','*.ova','*.qcow2','.config/discord/'}
On Thu 14 Nov 2019, Freddie Valdez via rsync wrote:
>
> Rsync 2.6.9
Wow, that's ancient. Released 06 Nov 2006
> Mac OS interacting with Windows servers.
>
> My Rsync command: rsync -rvz --exclude-from=exclude.txt source destination.
>
> I copy large files from server A to server B excluding mu
On Thu 14 Nov 2019, Pierre Bernhardt via rsync wrote:
> Am 14.11.19 um 10:54 schrieb Paul Slootman via rsync:
> > You need to specify the source directory as the link-dest directory.
>
> Hi, I tried it also because it's an old question which has never worked
> for me. In
On Thu 14 Nov 2019, L A Walsh via rsync wrote:
> Have a directory with a bunch rpms in it, mostly x86_64.
>
> Have another directory with a bunch, mostly 'noarch'.
>
> Some of the noarch files are already in the x86_64 dir
> and don't want to overwrite them. They are on the same
> physical disk
On Wed 30 Oct 2019, raf via rsync wrote:
>
> I have a task that rsyncs files from a list of
> candidate files (--files-from=). It's verbose (-v) and
It would be helpful to show the complete rsync command line.
Paul
--
Please use reply-all for most replies to avoid omitting the mailing list.
T
On Tue 01 Oct 2019, Bill Wichser via rsync wrote:
>
> Attached is the patch we applied. Since xxhash is in the distro, a
> dependency would be required for this RPM. If nothing else, perhaps the
> developers should just take a look as this could benefit many.
"The distro" is a bit vague for a t
On Thu 14 Feb 2019, Delian Krustev via rsync wrote:
> On Wednesday, February 13, 2019 6:25:59 PM EET Remi Gauvin
> wrote:
> > If the --inplace delta is as large as the filesize, then the
> > structure/location of the data has changed enough that the whole file
> > would have to be written out in
On Sun 03 Feb 2019, Philip Rhoades via rsync wrote:
>
> For some years I have been using rsync quite happily to send / retrieve
> files to / from SSHDroid Pro but recently I have started having a problem
> when transferring large numbers of file - I am pretty sure it started after
> upgrading from
On Sat 28 Apr 2018, Andras Nagy via rsync wrote:
> Summary: an xattr filter rule (e.g. --filter='-x! user.*’, which is suggested
> by the documentation) is treated as a file filter rule on the remote side.
I think that you're missing the point that filter rules affect the list
of files to be tra
On Mon 22 Jan 2018, Kevin Korb via rsync wrote:
> From man 2 select:
> int select(int nfds, fd_set *readfds, fd_set *writefds,
> fd_set *exceptfds, struct timeval *timeout);
>
> So, it is waiting for file descriptor #1 to become available with a 60
> second timeout which it is hitting.
Actually:
On Sun 08 Oct 2017, just subscribed for rsync-qa from bugzilla via rsync wrote:
>
> --- Comment #1 from Wayne Davison ---
> I've committed a fix for this into git. Many thanks for pointing this out.
> Sorry for how slow I've been lately.
Hey, I'm just happy you're still around :)
Paul
--
Ple
On Tue 05 Sep 2017, Vangelis Katsikaros via rsync wrote:
> On 08/30/2017 05:39 PM, Paul Slootman wrote:
> > On Wed 23 Aug 2017, Vangelis Katsikaros via rsync wrote:
> >
> >> abc 3797 3796 0 01:12 ?00:03:14 /usr/bin/rsync --compress
> >>
On Tue 15 Aug 2017, Joe Qiao via rsync wrote:
> Thanks so much for the quick reply, Kevin!
>
> I tried with ssh and --partial-dir, it looks the partial file still will be
> stored in local dir, but not in /tmp.
>
>
> Every 1.0s: ls -al /home/joe/rsync/ /tmp/
> Tue Aug 15 17:29:30 20
On Wed 16 Aug 2017, Vangelis Katsikaros via rsync wrote:
>
> I am having a problem with rsync freezing and I would like to collect the
> proper information while the problem happens. However, I would like to ask
> some clarifications.
>
> rsync-debug
> ===
>
> I see references of using
On Wed 23 Aug 2017, Vangelis Katsikaros via rsync wrote:
> abc 3797 3796 0 01:12 ?00:03:14 /usr/bin/rsync --compress
> --compress-level=9 --bwlimit=512k --recursive --delay-updates --quiet
> --update --exclude=/.* /SRC_PATH/ DEST_IP:/DEST_PATH/
Try running rsync without the
On Mon 12 Jun 2017, max.power--- via rsync wrote:
> How exactly does rsync determine that the copy has the incorrect timestamp
> and not the source file?
The source by definition is correct.
Paul
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or ch
On Fri 03 Mar 2017, Steve Dondley wrote:
> The directory I'm trying to copy from is: /home/blah/dir
>
> The symlink is /home/blah/dir/unwanted_symlinked_dir
>
> On Fri, Mar 3, 2017 at 8:10 AM, Paul Slootman wrote:
>
> > You don't say explicitly, is t
On Fri 03 Mar 2017, Steve Dondley wrote:
> I'm trying to rsync a directory from a server to my local machine that has
> a symbolic link to a directory I don't want to download. I have an
> "exclude" option to exclude the symlink which works fine. However, if I add
> a --copy-links option to the co
On Fri 20 Jan 2017, John Lane wrote:
>
> When you rsync a directory, say `$rsync mydir/ ...` with the trailing
> slash, the destination directory is changed to the ownership,
> permissions and timestamp of `mydir`.
> $ rsync -a a/ b/ c
> $ ls -ld c
> drwxr-xr-x 2 john users 4096 Jun 1
On Fri 18 Nov 2016, Harald Dunkel wrote:
>
> "--numeric-ids" is a lot of text and easy to be forgotten or
> misspelled.
>
> Since it is a highly important option for making backups of
> remote systems via rsync I wonder if "-N" could be introduced
> as an abbreviation for "--numeric-ids"? "-N" is
On Sat 29 Oct 2016, Samuel Williams wrote:
> I'm not proposing some additional characters to split on, but quite
> the opposite, to handle the backslash escaped spaces correctly and NOT
> split. Rest assured, there is no bug with the original escaping. For
> your edification:
>
> $ echo \I\'\m\ \
On Wed 26 Oct 2016, devz...@web.de wrote:
>
> since we are using rsync for backing up millions of files in a virtual
> environment, and most of the virtual machines run on SSD cached storage, i`d
> be curious how that negatively impacts lifetime of the SSD`s when we do rsync
> run every night f
On Tue 25 Oct 2016, devz...@web.de wrote:
>
> is there a reason why error code 255 is not mentioned in the manpage
> and wouldn`t it make sense to add "255 Unexplained Error" there
> for completeness ?
It wouldn't be unexplained then anymore, would it? :-)
Paul
--
Please use reply-all f
On Thu 20 Oct 2016, Samuel Williams wrote:
>
> I'm using Ruby's Shellwords module, which generates a string from an
> array, suitable for shell evaluation.
>
> Ruby's implementation prefers escaping whitespace with a backslash
> rather than quotes. However, this appears to cause some kind of issu
Try the transfer without -z.
Paul
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
On Wed 12 Oct 2016, Kip Warner wrote:
>
> I think the key insight was in the strace log which showed the select()
> call was timed out. If I knew what type of file descriptor it was being
> fed, I might have a clue. It might have been a socket or something on
> disk. I don't know.
You can use lso
On Mon 10 Oct 2016, Kip Warner wrote:
>
> The server the data is being uploaded to with the strace running on it
> has rsync version:
>
> $ rsync --version
> rsync version 3.0.9 protocol version 30
>
> The client reported:
>
> $ rsync --version
> rsync version 3.1.1 protocol
On Fri 01 Jul 2016, Stuart Anderson wrote:
> I would like to request that rsync -n to an rsync server target that is read
> only be supported rather than generating the following error,
> ERROR: module is read only
>
> The motivation is to allow the generation of a list of files against an rsync
On Fri 24 Jun 2016, Kevin Korb wrote:
> Again, --partial only means don't delete the incomplete file if rsync is
> aborted. Normally rsync will delete the incomplete file so you don't
> have bogus files laying around.
>
> When you rsync to or from a network mount to rsync that is a local copy.
>
On Fri 25 Mar 2016, John Long wrote:
>
> 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 minori
On Wed 20 Jan 2016, Wayne Davison wrote:
> equal. One possible improvement would be to skip the nanosecond check if
> the destination file has a nanosecond value of 0. That could possibly be
> improved if we figure out if a particular device ID supports nanoseconds
> somehow. I have a potential
On Wed 20 Jan 2016, Andrey Gursky wrote:
>
> I was just about to implement the same, since nanoseconds are taken
> into account when transferring, thus making it obvious not to ignore
Really? I thought the protocol only transmits seconds.
Paul
--
Please use reply-all for most replies to avoid
On Wed 30 Dec 2015, Paul Slootman wrote:
> -q seems to override -v completely, but when combined with --progress,
> a single newline is output when there are no updates transferred; but if
> a file *was* updated nothing at all is output.
>
> It seems that there might be some short
-q seems to override -v completely, but when combined with --progress,
a single newline is output when there are no updates transferred; but if
a file *was* updated nothing at all is output.
It seems that there might be some short-circuited code when nothing is
trasferred, but that a check for qui
The description for --compress-level=NUM does not give any indication
what values are permitted for NUM.
Paul
--- ./rsync.yo.orig 2015-12-30 11:47:24.180646652 +0100
+++ ./rsync.yo 2015-12-30 11:47:27.477198899 +0100
@@ -1907,7 +1907,9 @@
that will not be compressed.
dit(bf(--compress-le
On Mon 05 Oct 2015, Charles wrote:
>
> The question I want answering is "Does rsync need telling not to
> compress when SOURCE and DEST are both local or does it automatically
> choose a sane compression setting?"
If you don't ask rsync to compress, it won't compress...
That's different from tell
On Mon 13 Jul 2015, Andrew Gideon wrote:
>
> On the other hand, I do confess that I am sometimes miffed at the waste
> involved in a small change to a very large file. Rsync is smart about
> moving minimal data, but it still stores an entire new copy of the file.
>
> What's needed is a file sy
On Thu 30 Apr 2015, Kezhawe wrote:
> I can still read&write on the external hdd and on my laptop (which I
> have my gentoo there) I can't do anything on / because its filled up
> with /proc/kcore after "rsync failed"
You need to ignore /proc/kcore as (a) that's a virtual file that doesn't
reside
On Tue 14 Apr 2015, Hongyi Zhao wrote:
> I write a complex filter rules as follows:
>
> rsync -amvHPRSB131072 -n --delete --delete-excluded \
> -f +_dists/jessie/**binary-all/Packages.gz \
> -f +_dists/jessie/Release* \
> -f +_dists/jessie/**binary-amd64/Packages.gz \
> -f +_dists/jessie/**instal
On Tue 14 Apr 2015, Hongyi Zhao wrote:
> On Tue, 14 Apr 2015 09:32:10 +0200, Paul Slootman wrote:
>
> > On Tue 14 Apr 2015, Hongyi Zhao wrote:
> >>
> >> See the following commands:
> >>
> >> ___
> >>
&
On Tue 14 Apr 2015, Hongyi Zhao wrote:
>
> See the following commands:
>
> ___
>
> $ rsync -rmnv -f +_README -f -_* ftp.is.co.za::mirror/ftp.debian.org/
> ftp.us.debian.org/debian
>
> [snipped]
>
> receiving file list ... done
>
> sent 23 bytes received 9 bytes 1.42
On Tue 07 Apr 2015, Aron Rotteveel wrote:
> Anyone have any other ideas I could try to debug this issue? :)
You could try using the latest version of rsync? 3.1.1 was released some
time ago.
Paul
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or cha
On Sat 28 Feb 2015, ? ?? wrote:
>
> rsync version 3.0.9 protocol version 30
>
> rsync -a --exclude="tmp/*" /home/ /backup/home/
>
> It is necessary that the contents of the folder tmp copy, but the folder tmp
> in
> backup was created.
>
> If the folder /home/tmp/ is many millions of
On Thu 29 Jan 2015, Johan Kröckel wrote:
> I am looking for a way to start one rsync command with multiple destinations.
> My use case:
> I have one (slow) usb drive which should be synced to two other
> harddrives. It would be great if rsync could read one file which is to
> be copied to both har
On Wed 07 Jan 2015, Lenz Weber wrote:
> Where the local destination /data/snapshots is an NFS volume mounted with the
> flags
> (rw,noatime,addr=192.168.1.XX)
> and the source is a symlink to a zfs snapshot - that looks like this:
> /var/backups/mail ->
> /tank/mail/.zfs/snapshot/zfs-aut
On Wed 17 Dec 2014, David Jennings wrote:
> Hi all. I have a strange issue with sync'ing from a USB-attached ext4 file
> system on one machine, to a USB-attached ext3 file system on another.
> The sync works fine (a few thousand files). If I run it again straight away,
> or a few minutes later, r
On Wed 03 Dec 2014, yhu2 wrote:
> On 11/28/2014 09:41 AM, yhu2 wrote:
> >
> >thanks your reply, could you please send off official fix?
>
> or could you please tell me which release will include this patch. any
> comments would be appreciated!
The git repository is browseable, the patch for this
On Sat 04 Oct 2014, Paul Slootman wrote:
> > Only the modified file was backed up. However the whole file was copied,
> > not just the new things. :-(
>
> Why do you say this?
Oops, didn't read Kevin's followup and didn't notice the rsync over two
"local&qu
On Thu 02 Oct 2014, Juan Carlos Valle Sandoval wrote:
> I have changed the script to:
>
> rsync.exe -ai --size-only --progress
> --log-file=/cygdrive/v/notes/archive/RSyncLogFile.txt
> /cygdrive/d/%username%/notes/archive /cygdrive/v/notes/
You could still try the other suggestion of --modify-wi
On Mon 15 Sep 2014, Kevin Korb wrote:
>
> I would never operate in a manner that only has 5-6 days of old
> backups. The backups that I am deleting are more than a year old.
I keep the Sunday backups for a month, the 1st of the month backups for
a year.
The other daily backups are expired after
On Sat 26 Jul 2014, Kevin Korb wrote:
>
> > I just moved my home partition to a new harddisk w/more space.
>
> Home Partition? Are we in 1995? Why would you have a partition
> mounted anywhere other than /boot ?
Didn't we just have this discussion already recently?
There are valid reasons to h
On Sat 15 Feb 2014, Perry Hutchison wrote:
> Hiroyuki Ikegami wrote:
> > 2014-02-15 7:39 GMT+09:00 Grozdan :
> > > Yesterday, I changed my rsyncd.conf file to add one more module to it.
> > > Then I sent a kill -HUP $pid signal to rsync running in daemon mode,
> > > but what gives? It just died so
On Fri 14 Feb 2014, Matthias Schniedermeyer wrote:
>
> You mixed the options from "remote shell" with "rsync daemon".
> Rsync is used either as 'rsync over SSH'(/remote shell) OR daemon-mode.
Matthias,
Ik recommend you check out the "USING RSYNC-DAEMON FEATURES VIA A
REMOTE-SHELL CONNECTION" part
On Mon 10 Feb 2014, Lorenz wrote:
> grep -v "#" /etc/rsnapshot | grep [a-z]
> i.e. the /etc/rsnapshot minus the comments and the empty lines:
I'd recommend using 'grep .' to find non-empty lines... shorter and more
accurate :-)
> rsync_long_args -ev --rsync-path=/home/backupuser/rsync-wrap
On Sun 02 Feb 2014, Hongyi Zhao wrote:
>
> But I've tried the following methodes based on your suggestion and get
> different results:
>
>
> werner@debian:~$ rsync -a --exclude '/*/*/*/*'
> rsync://ftp.cn.debian.org/debian | wc -l
> 1798
> werner@debian:~$ rsync -a --exclude '/*/*/*/
On Sun 02 Feb 2014, Hongyi Zhao wrote:
>
> I want to list the contents on the remote rsync server only to n, say,
> 2 level deep.
>
> In my case the the server is rsync://ftp.cn.debian.org, and I want to
> list all of the stuff in the following subdirectory only to 2 level
> deep:
>
> rsync://ft
On Tue 07 Jan 2014, Ashley M. Kirchner wrote:
> On Tue, Jan 7, 2014 at 9:44 AM, Paul Slootman wrote:
>
> > rsync will not touch files that have been --exclude'ed; unless you also
> > specify --delete-excluded . So just specify those LIVE-only files in
> > your exclud
On Tue 07 Jan 2014, Ashley M. Kirchner wrote:
>
> My issue is with the --delete part. While I want the procedure to delete
> extraneous files from the LIVE server when they are removed from the DEV
> one, there are a few files on LIVE that do not and will never exist on the
> DEV server, however
On Wed 18 Dec 2013, Kevin Korb wrote:
> Also, rsync's -c is rather dumb as it computes checksums for files
> that have different sizes so they can't possibly be the same and it
> computes checksums for files that only exist on one end and therefore
> has nothing to compare them to.
The list of fi
On Tue 03 Dec 2013, Kevin Korb wrote:
>
> Sure. Simply put, you can just change ext[23] to ext4 in fstab and it
> will just work. Faster even.
Just be very sure that you have ext4 support in your kernel, otherwise
you have a problem. ext4 should be listed in /proc/filesystems .
Of course, the r
On Fri 01 Nov 2013, Carlos Carvalho wrote:
> Happened again:
>
> Oct 31 15:55:49 sagres kernel: denied resource overstep by requesting 8392704
> for RLIMIT_STACK against limit 8388608 for /usr/local/bin/rsync[rsync:80954]
> uid/euid:1011/1011 gid/egid:1011/1011, parent
> /usr/local/bin/rsync[r
On Sun 13 Oct 2013, Jed Brown wrote:
> The man page describes options --chown, --usermap, and --groupmap, but
> these seem to be silently ignored beyond validating that the user and
> groups do indeed exist. Is the following supposed to work?
No, because you're not running the rsync command as t
On Mon 30 Sep 2013, thomas veymont wrote:
>
> ie. any modules declared in mymodules1/ will use users/passwords in
> secret1.inc whereas mymodules2/ modules will use secret2.inc.
>
> is it the right way to implement this ?
Well, the "secrets" parameter is listed under "MODULE PARAMETERS" in the
r
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
>
> I read your sentence differently:
>
> > If he can make a HARD link to the shadow file, then he can already
> > read it - and worse.
>
> My understanding of your sentence says:
> The ability to hardlink, means that anyone can read any file t
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
>
> BUT there is no direct vulnerability in that, only processes after that
> (like backup/rsync) can make a vulnerability out of it.
... which is what I already wrote.
Paul
--
Please use reply-all for most replies to avoid omitting the maili
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
> >
> > > Hardlinking a file doesn't change it's owner/group/permission
> > > (All Hardlinks have the same user/group/permissions).
> >
> > I never said that.
>
> You implied that by your assertion that you suddenly can read a file
> after har
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
> That aside that's not what i meant.
That's the problem with one-word answers, people have to guess what you
mean.
> Hardlinking a file doesn't change it's owner/group/permission
> (All Hardlinks have the same user/group/permissions).
I neve
On Tue 13 Aug 2013, Matthias Schniedermeyer wrote:
> On 13.08.2013 09:52, Paul Slootman wrote:
> > On Tue 13 Aug 2013, Sherin A wrote:
> >
> > > But if a user create a
> > > hard link to /etc/shadow from his home dir , and he request a restore ,
> >
On Tue 13 Aug 2013, Sherin A wrote:
> But if a user create a
> hard link to /etc/shadow from his home dir , and he request a restore ,
> then he can read the shadow files and decrypt it .
If he can make a HARD link to the shadow file, then he can already read
it - and worse.
Paul
--
Please us
On Mon 01 Jul 2013, garvit sharma wrote:
> please tell me for what time will rsync wait if the connection breaks
> during the file transfer ??
Try the manpage:
--timeout=TIMEOUT
This option allows you to set a maximum I/O timeout in seconds.
If no data is transferred for
On Mon 27 May 2013, Joseph L. Casale wrote:
> On Linux, an rsync command and exclude_file contents of:
>
> # cat exclude_file
> /etc/alsa
> # rsync -a --delete --delete-excluded --exclude-from=exclude_file /etc
> server::module
>
> properly excludes /etc/alsa but not any file within /etc's dire
On Tue 21 May 2013, Allen Supynuk wrote:
>
> ## 1) Start with an empty filesystem
>
> $ df -h .
Note that you need to be using "btrfs filesystem df ."
for reliable numbers; the normal df does not take into account
background cleanups etc.
Paul
--
Please use reply-all for most replies to avoid
On Wed 15 May 2013, Brian K. White wrote:
> I did in the case when it was only one pattern, but that was just a
> simplified example.
>
> The actual job involves too many include and exclude patterns to use
> --include & --exclude, or even --include-from and --exclude-from,
> because the patterns
On Wed 15 May 2013, Brian K. White wrote:
> > rsync -avz /foo/ ${DEST}::root/foo/
>
> This syntax does work in his case, and is easier to read, because it
> ends up using the exact same specification "/foo/" and "/foo/" for
> both source and dest, but the syntax I had was also correct. I no
> lon
On Wed 15 May 2013, Brian K. White wrote:
> Consider the following directory structure
>
> /foo/aaa/*/*
> /foo/bbb/*/*
> /foo/ccc/*/*
>
> I want to sync all of /foo,
> but exclude /foo/aaa
> rsync -avz /foo ${DEST}::root
Firstly, I always recommend that with directory transfers you add a
trail
On Tue 30 Apr 2013, Gauri Senad wrote:
>
> I am compiling rsync-3.0.9 in my build system (which is for 2.6.10 linux
> kernel. I am using windriver build system), compilation is failing due to
> size of “uint32” and “uint16” was computed wrongly during configuration.
Hmm, it took some googling to
On Mon 29 Apr 2013, Kevin Korb wrote:
>
> Simply put, if you have something that is screwing with your file data
> without touching your time stamps then you have been infected with a
> rootkit. You should be thanking rsync for not backing up your
As he's running QNX I don't expect he's infected
1 - 100 of 739 matches
Mail list logo
