similar to: 2.2.7 compile error using --with-acl-support on debian

Dear Andrew Tridgell, i cant compile the 2.2.1-9 package --with-acl-support, beacuse HAVE_SYS_ACL_H has wrong settings somewhere. i cant fix the bug, i just comment out the #ifdef HAVE_SYS_ACL_H line in the source/include/includes.h for a (i hope) good compilation. i use acl 1.1.2 from sgi, and the latest debian woody packages. Regards. Imre Szollosi mailto:szollosi@elme.hu

[username@localhost source]# ./configure --with-fhs --prefix=/usr --sysconfdir=/etc --with-privatedir=/etc/samba --with-lockdir=/var/state/samba --localstatedir=/var --with-netatalk --with-smbmount --with-pam --with-syslog --with-sambabook --with-utmp --with-acl-support > ~/myconfig.out 2>&1 [username@localhost source]# cat ~/myconfig.out | grep acl checking for sys/acl.h... yes

Great, thanks Arjen! Now we need an autoconf test to set HAVE_IPV6 automatically. I will look into what functionality needs to be tested; the test can be refined as problems arise later. -- Peter Arjen de Korte wrote: > > Author: adkorte-guest > Date: Sat Jan 6 19:39:08 2007 > New Revision: 710 > > Modified: > trunk/ChangeLog > trunk/clients/upsc.c >

With the Ipv6 patch (r708), I get: upsclient.c: In function `upscli_connect': upsclient.c:469: `AI_ADDRCONFIG' undeclared (first use in this function) upsclient.c:469: (Each undeclared identifier is reported only once upsclient.c:469: for each function it appears in.) Even if it doesn't break IPv4 support, it may break portability, as IPv6 seems to require specific functions that are

Hi- I am experiencing some odd behavior with ACLs with winbindd using Samba 2.6 on Debian Woody (kernel version 2.4.18). 1. I am unable to alter permissions from Win2K clients using the Properties->Security interface. Is this normal? I get the "Unable to save Permission Changes on new Folder. Access is denied." message. This occurs with all accounts, both privileged and

--- fuse/test-fuse.c | 5 ----- 1 file changed, 5 deletions(-) diff --git a/fuse/test-fuse.c b/fuse/test-fuse.c index 2876dc4..1e18a75 100644 --- a/fuse/test-fuse.c +++ b/fuse/test-fuse.c @@ -249,9 +249,7 @@ test_fuse (void) unsigned u, u1; int fd; struct timeval tv[2]; -#if 0 struct timespec ts[2]; -#endif acl_t acl; char *acl_text; @@ -574,8 +572,6 @@ test_fuse (void)

Hi, this is the first time I've tryed to build a 64 Bit Version with acl's enabled - so I expect I could duplicate this with older versions too... Here's the build info: System: AIX 6100-07-01-1141 Compiler: IBM xlc CC=xlc_r -g CXX=xlC_r CFLAGS=-qmaxmem=-1 -DSYSV -D_AIX -D_AIX32 -D_AIX41 -D_AIX43 -D_AIX51 -D_AIX52 -D_AIX53 -D_AIX61 -D_ALL_SOURCE -DFUNCPROTO=15 -O

https://bugzilla.samba.org/show_bug.cgi?id=7865 Summary: files or dirs with more than 16 ACLs are not rsynced correctly Product: rsync Version: 3.0.7 Platform: IA64 OS/Version: HP-UX Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org

I have compiled both my kernel (2.4.17) and samba (2.2.3a) to support ACL/EAs. It looks like it has gone well, but I get one message that worries me, but I don't know if it should or not. checking whether to support ACLs... checking for acl_get_file in -lacl... yes checking for ACL support... yes Using posix ACLs checking for acl_get_perm_np... no As you can see, the last line is where my

Problem is apparently with locking issues, disabled oplocks in the [general] section, and the problem actually got worse... Here's what happens: User-A part of group1, opens Excel file off of share, saves, exits... User-B (or even User-A for that matter) tries to re-open same file, get error stating it's locked and can only open for read-only access... Both users in the same group, and

Hello, I am the guy behind the ext2/ext3 patches for Extended Attributes and ACLs, and I've recently been asked about ACL support in rsync by Eric. Upon investigating I found that you have an ACL patch against rsync-2.5.5 [1]. I also found some other postings to rsync@lists.samba.org concerning rsync and ACLs [3]. Are there any plans for finalizing an integrating that rsync ACL patch? I

This is a PoC patch for NFSv4/ZFS ACLs. The objective of the patch is that rsync --acls support NFSv4/ZFS ACLs without requiring a new command line option NFSv4 ACLs can't be represented using POSIX draft ACLs, if an NFSv4 ACL is present a separate POSIX draft ACL will not be present and there are new APIs to access NFSv4 ACLs. So we need to distinguish between NFSv4 ACLs and POSIX ACLs in

The existing APIs guestfs_stat, guestfs_lstat and guestfs_lstatlist return a stat structure that contains atime, mtime and ctime fields that store only the timestamp in seconds. Modern filesystems can store timestamps down to nanosecond granularity, and the ordinary glibc stat(2) wrapper will return these in "hidden" stat fields: struct timespec st_atim; /* Time of last

############################# In German : Hallo, gibt es da Jemanden der mir den folgenden Text vielleicht ein bischen besser erkl?ren kann? Habe dies aus dem Samba Developers Guide. Warum mach ich das nun? Ich habe ein Problem: Ich will das jedes mal wenn ein User versucht einen Ordner in der Freigabe zu verschieben oder umzubenenner, der nicht leer ist, eine Fehlermeldung auf dem Client

Hi, I am using kernel 3.7-rc6. I have written a test application for extended attributes and have for some folders a wired behaviour: #include <stdio.h> #include <string.h> #include <attr/xattr.h> char attrs[1024]; ssize_t attrslen; int i; char value[1024]; ssize_t valuelen; int main(int argc, char *argv[]) { if (argc != 2) { fprintf(stderr, "Syntax: testxattr

Hi, from time to time, there have been requests (or attempts, like the mingw port posted on the list some months ago) to make libguestfs work on OSes different than Linux. Of course this would imply using a fixed appliance, since it is currently heavily dependent on Linux. The attached series provides some easy changes in this direction, resolving some of the easy issues found in porting to

if((group_c = *lp_force_group(snum))) { BOOL is_guest = False; some lines deleted token = create_nt_token(uid, gid, current_user.ngroups,current_user.groups, is_guest); must_free_token = True; } set_sec_ctx(uid, gid, current_user.ngroups, current_user.groups,token); /* * Free the new token (as set_sec_ctx