Displaying 20 results from an estimated 300 matches similar to: "patch: --force-change for hard links"
2012 May 07
0
Solved problem with hard links and schg flag under FreeBSD
Hi!
Using rsync under FreeBSD with hard links and files having schg set
result in EPERM "Operation not permitted". This behavior can be observed
if rsyncing /usr/bin/.
The patch fileflags.diff tries to deal with this situation but changes
the flags of the parent directory only. It doesn't change the flags of
the files itself.
do_link() in syscall.c has to be fixed. The
2008 Apr 14
0
[PATCH] xattrs not set on locked files that already exist on target
Working with rsync 3.0.2, it appears that rsync isn't unlocking files
before setting the file attributes when those files already exist.
This generates error messages on subsequent such as:
rsync: rsync_xal_set: lsetxattr("locked_file","test_xattr") failed:
Operation not permitted (1)
rsync: rsync_xal_clear:
2008 Feb 15
4
Revised flags patch
Hi,
first of all, sorry for taking so long. Unfortunately, some other tasks
kept coming up. Anyway, attached is the version of the flags patch, that
is based on the one I'm using with 2.6.9. It is against the rsync-3.0.0pre9
release.
I've included the option name change from the repository, so the
option is now called --fileflags. Improved from the previously
distributed version is the
2002 Jan 07
0
rsync-2.5.1 / updated syscall.c "const" patch
Operating System: OpenVMS ALPHA V7.3
Compiler: Compaq C T6.5
Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE)
syscall.c is missing the "const" qualifiers for several of it's
functions. This patch should supercede the previous patch I submitted.
This was discovered while working on resovling the conflicts between
signed and unsigned values.
-John
wb8tyw@qsl.network
Personal
2008 Jun 25
2
DO NOT REPLY [Bug 5565] New: xattrs not set on locked files that already exist on target
https://bugzilla.samba.org/show_bug.cgi?id=5565
Summary: xattrs not set on locked files that already exist on
target
Product: rsync
Version: 3.0.3
Platform: Other
OS/Version: Mac OS X
Status: NEW
Severity: normal
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2011 Oct 17
2
Reading data with 'awk' - basics?
Hi,
I had a large file for which I require a subset of rows. Instead of reading
it all into memory, I use the awk command to get the relevant rows. However,
I'm doing it pretty inefficiently as I write the subset to disk, before
reading it into R. Is there a way that I can read it into an R object
without writing to disk? For example, this is what I do currently:
## write test sample file
2009 Sep 03
1
encoding problem using xml package
Dear list
I tried to read an xml file using the xml package. Unfortunately, some encoding problems occure. E.g. german Umlaut will be red correctly. I assume that the occurs due to (internal?) conversion to utf-8. To illustrate the problem, I have wrote to xml files.
File Test 1
-----------
<?xml version="1.0" encoding="ISO-8859-1"?>
<Daten>
<ITEM>
2017 Jul 14
0
Help with R script
@Don your solution does not solve Vijayan's scenario 2. I used spread and
gather for that.
An alternative solution to insert mising Fval - picking up with Don's
newtst - is
newtst <- c("FName: fname1", "Fval: Fval1.name1", "FName: fname2", "Fval:
Fval2.name2", "FName: fname3", "FName: fname4", "Fval: fval4.fname4")
2008 Mar 04
1
Several changes missing from [HEAD] fileflags.diff
Looking at http://rsync.samba.org/ftp/rsync/patches/fileflags.diff --
It looks like the changes from fileflags-fixes.diff patch were applied
to the patch from http://rsync.samba.org/ftp/rsync/rsync-patches-3.0.0.tar.gz
, but this entire chunk of the that original diff file was lost:
> diff -up a/config.h.in b/config.h.in
> --- a/config.h.in
> +++ b/config.h.in
> @@ -64,6 +64,9 @@
2017 Jul 13
2
Help with R script
Using Ulrik?s example data (and assuming I understand what is wanted), here is what I would do:
ex.dat <- c("FName: fname1", "Fval: Fval1.name1", "Fval: ", "FName: fname2", "Fval: Fval2.name2", "FName: fname3")
tst <- data.frame(x = ex.dat, stringsAsFactors=FALSE)
sp <- strsplit(tst$x, ':', fixed=TRUE)
chk <-
2017 Jul 13
0
Help with R script
Hi Vijayan,
one way going about it *could* be this:
library(dplyr)
library(tidyr)
library(purrr)
ex_dat <- c("FName: fname1", "Fval: Fval1.name1", "Fval: ", "FName:
fname2", "Fval: Fval2.name2", "FName: fname3")
data.frame(x = ex_dat) %>%
separate(x, c("F1", "F2"), sep = ": ") %>%
filter(F2
2009 Mar 11
0
Odd issue with locked directories and Mac OS X
Some of my users have reported problems with rsync puking on locked
folders. The errors typically look like this:
rsync -aNHAXx --fileflags --force-change --no-inc-recursive / /Volumes/
Backup
> rsync: mkstemp "/Volumes/SCSI Backup/Users/Ken/Library/Caches/
> Metadata/Safari/Bookmarks/..DS_Store.N9xtNy" failed: Operation not
> permitted (1) (51)
> rsync: mkstemp
2004 Apr 11
1
fchmod in do_mkstemp? (patch included)
Why is do_mkstemp fchmod-ing the temporary file? I was not able to
figure this out from the CVS logs or my searches in the mail archives.
Currently, do_mkstemp does this (*):
mkstemp temporary file (which leaves it with 0600)
fchmod temporary file (final perm & 0700)
And then later it gets renamed to the final name and permissions set
to what they are supposed to be.
(*)
2010 Nov 11
1
lsetxattr() failed: Operation not permitted on symlinked locked directory
Hi,
I am using rsync 3.0.7 from MacPorts under Mac OS X 10.6.4. I am getting the error in the subject in the presence of a symlinked and locked directory with an extended attribute. To reproduce:
mkdir src
mkdir dst
mkdir src/dir-with-ea-and-uchg
./xattr-util --set mamma.mia "How about a nice pizza?" src/dir-with-ea-and-uchg
cd src
ln -s dir-with-ea-and-uchg/ symlink-to-dir
chflags uchg
2011 Mar 16
3
[Bug 8019] New: Various improvements to the fileflags patch
https://bugzilla.samba.org/show_bug.cgi?id=8019
Summary: Various improvements to the fileflags patch
Product: rsync
Version: 3.0.8
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: core
AssignedTo: wayned at samba.org
ReportedBy: mike at bombich.com
2023 Sep 03
2
Why try to update (some) permissions which are the same?
On the source system:
$ rsync --version
rsync version 2.6.8 protocol version 29
Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others.
<http://rsync.samba.org/>
Capabilities: 64-bit files, socketpairs, hard links, ACLs, symlinks, batchfiles,
inplace, IPv6, file flags, 32-bit system inums, 64-bit internal inums
...
$ ll -d fcst-200[89] fcst-201[01]
dr-xr-xr-x
2008 May 31
1
rsync 3.0.2 with --fileflags on FreeBSD: cannot rsync hardlinked immutable files
Hi *,
it seems rsync with --fileflags isn't able to work on (already)
hardlinked and immutable ("schg") files on FreeBSD. The following
scripts will create a simple example for this behaviour:
--------------------------------------------------------------
#! /bin/sh
#
#
set -x
DIR="/var/tmp/rsync_$(date +%s)/"
mkdir "${DIR}/"
# Preparing dir_A
mkdir
2010 Sep 22
0
fileflags, hardlinks and FreeBSD
I have an rsync daemon running on a FreeBSD 7.3 system. It is running
rsync 3.0.4 with fileflags enabled. I have the following six files on it
which are all hardlinks and have the immutable flag set:
6830483 -r-sr-xr-x 6 root wheel schg 33268 Jan 6 2005 chfn
6830483 -r-sr-xr-x 6 root wheel schg 33268 Jan 6 2005 chpass
6830483 -r-sr-xr-x 6 root wheel schg 33268 Jan 6 2005
2006 May 04
6
DO NOT REPLY [Bug 3752] New: rsync unusable with EncFS filesystem
https://bugzilla.samba.org/show_bug.cgi?id=3752
Summary: rsync unusable with EncFS filesystem
Product: rsync
Version: 2.6.8
Platform: x86
OS/Version: Linux
Status: NEW
Severity: critical
Priority: P3
Component: core
AssignedTo: wayned@samba.org
ReportedBy: micheala@jacey.org
2011 Jan 11
1
--detect-renamed for mac users : proposition of a modification
Hello,
Object of my mail :
1/ stick a problem of incompatibylity between 2 patches (fileflags.diff &
detect-renamed.diff)
2/ proposition of a correction
I wanted to run rsync on a mac (OS X 10.6.5) with the --detect-renamed
option.
I therefore tried to compile rsync with the 3 relevant patches :
- fileflags.diff
- crtimes.diff
- detect-renamed.diff
But the patch detect-renamed.diff is