Dear bacula users,
I experimented a few days with "aclsupport=yes" for a SuSE 10.0 server
and client -- wondering why my acls never got restored. Now I realized
that the rpms for SuSE on sourceforge.net are compiled without acl support:
bruch:~ # ldd /usr/sbin/bacula-fd
linux-gate.so.1 => (0xffffe000)
libz.so.1 => /lib/libz.so.1 (0x4003a000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x4004d000)
libdl.so.2 => /lib/libdl.so.2 (0x4005f000)
libssl.so.0.9.7 => /usr/lib/libssl.so.0.9.7 (0x40063000)
libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0x40093000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x4018d000)
libm.so.6 => /lib/tls/libm.so.6 (0x4026a000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40290000)
libc.so.6 => /lib/tls/libc.so.6 (0x4029b000)
/lib/ld-linux.so.2 (0x40000000)
I compiled the sources for myself and had no problems with acls on xfs
no more.
Wouldn't it be a good idea to include acl support in all rpms?
--
Regards
Christoph
________________________________________________________________________
Christoph Litauer [EMAIL PROTECTED]
Uni Koblenz, Computing Center, http://www.uni-koblenz.de/~litauer
Postfach 201602, 56016 Koblenz Fon: +49 261 287-1311, Fax: -100 1311
PGP-Fingerprint: F39C E314 2650 650D 8092 9514 3A56 FBD8 79E3 27B2
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
