search for: extattrs

...xattr.h... no checking sys/xattr.h usability... no checking sys/xattr.h presence... no checking for sys/xattr.h... no checking sys/extattr.h usability... yes checking sys/extattr.h presence... yes checking for sys/extattr.h... yes ... checking whether to support extended attributes... Using FreeBSD extattrs I then run make where I get the following error: ... gcc -I. -I. -static -DHAVE_CONFIG_H -Wall -W -I./popt -c lib/pool_alloc.c -o lib/pool_alloc.o gcc -I. -I. -static -DHAVE_CONFIG_H -Wall -W -I./popt -c lib/sysacls.c -o lib/sysacls.o gcc -I. -I. -static -DHAVE_CONFIG_H -Wall -W -I./popt -c lib...

Hello trusty rsync list, I'm excited about --fake-super as it will replace too much work with none at all. I have gotten it to work under linux and I have a fair grasp with what is happening there. I have a problem, though, and that is, in the long term, I'll need to archive my Linux systems not to a Linux box, but to a Solaris 10 box. I understand that Solaris does have extended

Hello I want to use GlusterFS as a nfs substitute for a FreeBSD Server and Linux clients. The FreeBSD-server should export several directories. One of these directories contains the home-directory for the client-mashines. The problem is that my GlusterFS setup isn't very stable and crashes quite often. It is less stable, when more than one volume is mounted, but even when only one volume is

Hi. I'm attempting to compile rsync 2.6.9 with both the acls & xattr patches on an MacBook pro (ie: Intel processor), with the latest Apple Developer Tools. While this is OS X client, I've enabled acls via "sudo /usr/bin/fsaclctl -p / -e" and rebooted, prior to attempting to compile rsync. Is there something else inherent in OS X Server perhaps, that I'm still

meminfo.c32: Remove unneeded 'x' characters from output. Commit 5932f124 ("com32: change '%llx' to use PRIx64", committed on 2015-01-06) adds 1 "x" character per each of the 3 hex output columns for the 'INT 15h e820' value(s) in meminfo.c32. These 3 extra "x" characters are not really needed in this context, and they can make the resulting

Maybe rsync could support extattrs on non-supporting fs's with a .<fn>.xattr file stored at the same place as the <fn>: If a user used a switch to emulate 'xattrs', then on a fs that didn't support real .xattrs one could still ACL and other .xattr info. If a user ran rsync w/o that switch such fi...

This patch adds all the missing commonly used UNIX attributes: st_dev, st_ino, st_nlink, st_rdev, st_blocks, st_blksize, st_ctime. In addition it extends st_atime and st_mtime to 64bits, and adds nanosecond resolution to all three timestamps. This is implemented as an extension to the ATTR message. This patch alone is sufficient for SSHFS to be able to use these attributes. The following two

On an i686 with glibc 2.5 installed I'm not able to compile rsync 3.0.2 and later. rsync 3.0.0 was no problem, this compiled. Also on an x86_64 with glibc 2.7 installed rsync compiled. Here is a script of the failing comilation: Script started on Sat May 10 07:33:39 2008 teddy@mail /usr/src/rsync-HEAD-20080508-0612GMT $ mkdir build teddy@mail /usr/src/rsync-HEAD-20080508-0612GMT $ cd build

Hello. Use <inttypes.h> PRIx64 instead of llx to get rid of gcc warning format ?%llx? expects type ?long long unsigned int?, but argument 2 has type ?uint64_t? -- MartinS diff --git a/com32/gpllib/acpi/xsdt.c b/com32/gpllib/acpi/xsdt.c index 208abc6..228b6c3 100644 --- a/com32/gpllib/acpi/xsdt.c +++ b/com32/gpllib/acpi/xsdt.c @@ -63,7 +63,7 @@ int parse_xsdt(s_acpi * acpi) /*

https://bugzilla.mindrot.org/show_bug.cgi?id=1953 TJ Saunders <tj at castaglia.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tj at castaglia.org --- Comment #6 from TJ Saunders <tj at castaglia.org> --- Instead of using custom SFTP

(FreeBSD 6.1-RELEASE) tar xzvf rsync-2.6.8.tar.gz cd rsync-2.6.8.tar.gz patch < patches/acls.diff patch < ./patches/xattrs.diff ./prepare-source ./configure --enable-acl-support --enable-xattr-support --disable-debug --with-rsyncd-conf=/usr/local/etc/rsyncd.conf --bindir=/usr/local/bin Couldn't be more simple. But...when I try to 'make' : (snip) gcc -I. -I. -g -O2

If the code to convert FinderInfo is in a version later than 4.3.6 then I can request FreeNAS update their version. Can you let me know? Thanks! -Scott On Wed, Apr 27, 2016 at 1:49 PM, Ralph Boehme <slow at samba.org> wrote: > On Wed, Apr 27, 2016 at 10:50:12AM -0700, Scott Call wrote: > > (apologies to Ralph, I replied directly to him w/o copying the lists, so > > here we

https://bugzilla.samba.org/show_bug.cgi?id=7625 Summary: "Don't know how to make ./*.c" Product: rsync Version: 3.0.7 Platform: s390 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: sebastian.hoffman at

Skipped content of type multipart/alternative-------------- next part -------------- # ./configure configure.sh: Configuring rsync 3.0.1 checking build system type... hppa2.0w-hp-hpux11.11 checking host system type... hppa2.0w-hp-hpux11.11 checking target system type... hppa2.0w-hp-hpux11.11 checking for gcc... no checking for cc... cc checking for C compiler default output file name... a.out

Could this be why I am getting a problem with the initial configure? checking for Active Directory and krb5 support... yes checking for ldap_initialize... (cached) no configure: error: Active Directory support requires ldap_initialize -------------- next part -------------- SAMBA VERSION: 3.2.0 LIBREPLACE_LOCATION_CHECKS: START checking build system type... sparc-sun-solaris2.9 checking

Hi Folks, I'm trying to debug an issue that I've found while attempting to qualify GlusterFS for potential distributed storage projects on the FreeBSD-11.1 server platform - using the existing package of GlusterFS v3.11.1_4 The main issue I've encountered is that I cannot add new bricks while setting/increasing the replica count. If I create a replicated volume "poc"

Hi All, I'm having problems compiling a newer version of samba (3.3.x or 3.4.x) on solaris 9. We are currently running 3.0.23d and have been putting off upgrading for far to long. I've tried gcc and sun studio 12 cc with the same issues when it comes to compiling dbwrap.c. I can't seem to find anything on google that's related to my issue. Here's my configure line when

I'm having trouble compiling Samba 3.5.2 on AIX 5.3 TL10 SP1. I'm compiling Samba with ADS support against a locally installed Heimdal 1.3.2 Kerberos installation and I'm getting a failure while compiling clikrb5.c This is using the IBM xl_C compiler. Below is the complete build logs. I'm able to get around the error if I undef HAVE_SHORT_KRB5_MK_ERROR_INTERFACE in the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have recently tried to build samba4 on osx from the latest git pull I have had a build error while trying to compile this. I have make clean, and reconfigured this. [ 480/2253] Compiling lib/ldb/common/ldb.c ../lib/ldb/common/ldb.c: In function ?ldb_init?: ../lib/ldb/common/ldb.c:103: warning: ?tevent_loop_allow_nesting? is deprecated (declared

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have just pulled the latest git on my OSX 10.6.4 install. I am attempting to build samba4 and i get this error. [ 411/2152] Compiling ../lib/tdb/common/transaction.c ../../lib/tdb/common/transaction.c: In function ?transaction_sync?: ../../lib/tdb/common/transaction.c:552: error: implicit declaration of function ?fdatasync? Waf: Leaving