On 2/2/08, Hydro Meteor <[EMAIL PROTECTED]> wrote:
>
>
> On 2/2/08, Ralf Gross <[EMAIL PROTECTED]> wrote:
> >
> > Hydro Meteor schrieb:
> > >
> > > For those interested in running Bacula 2.2.8 on Mac OS X 10.5.1(Leopard)
> > > including Leopard Server, I can confirm, with a simple Bacula backup
> > and
> > > restore test, that Bacula does not capture or restore file system
> > resources
> > > that have Access Control List (ACL) metadata only. Files with Mac OS X
> > > Extended Attributs (EAs) which EAs are not ACLs seem to be captured
> > and
> > > restored just fine.
> >
> > You used the 'ACL Support = yes' directive?
>
>
> Ralph, thank you.
>
> Yes, I did include aclsupport=yes in the FileSet resource.
>
As a follow up, I tried several variations. For example, the File Daemon I
had configured to run as the root user (per best practice suggested by the
Bacula documentation and community), but just in case there was an issue, I
also ran the Storage and Director daemons as the root user (all on the same
system -- on Leopard Server -- even though logically there was really not
much sense in doing this, but I wanted everything as root to see if the root
user was the only user that could capture ACLs on the file system). The
change to root did not make a difference.
The ACL metadata appears not to be captured by the Bacula File Daemon. For
example, after doing a backup, in the Bacula console, I typed the "dir"
command (instead of the "ls") command and noticed the lack of the expected
"+" character (in the yellow highlighted privileges output of "dir" in the
Bacula Console below):
drwx------ 2 hydro staff 136 2008-02-02 16:43:50
*/Users/hydro/Movies/
With the aclsupport=yes for the FileSet resource, I am now at a loss. Mac OS
X Server (Leopard) is considered POSIX.1e compliant:
http://www.apple.com/macosx/technology/unix.html
Leopard is an Open Brand UNIX 03 Registered Product, conforming to the SUSv3
> and POSIX 1003.1 specifications for the C API, Shell Utilities, and
> Threads. Since Leopard can compile and run all your existing UNIX code, you
> can deploy it in environments that demand full conformance — complete with
> hooks to maintain compatibility with existing software.
>
and:
http://developer.apple.com/documentation/Darwin/Reference/Manpages/man3/acl.3.html
*acl* -- introduction to the POSIX.1e ACL security API
>
>
According to the Bacula User's Guide, POSIX 1003.1 should be supported on
Mac OS X Leopard:
aclsupport=yes—no The default is no. If this option is set to yes, and
> you have the POSIX libacl installed on your system, Bacula will
> backup the file and directory UNIX Access Control Lists (ACL) as
> defined in IEEE Std 1003.1e draft 17 and "POSIX.1e" (abandoned).
>
I wonder, what is required to version Bacula's ACL support to work with
Apple's POSIX.1e implementation?
Thank you,
Hydro
Also, ACL support was noted and enabled when I ran configure when
> configuring the Bacula 2.2.8 source on Leopard Server.
>
> There was a discussion regarding extended attributes on the dev list
> > recently.
> >
> > http://thread.gmane.org/gmane.comp.sysutils.backup.bacula.devel/11066
>
>
> Interesting.
>
> Thanks,
>
> Hydro
>
>
> Ralf
>
>
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
