On 03/13/17 07:18, Stuart Henderson wrote:
> On 2017/03/13 08:07, Wanderlei Huttel wrote:
>> Good Morning
>>
>> This problem in ACL is only in OpenBSD or in any system?
>
> It will be any where Bacula doesn't have ACL/XATTR support. In the case
> of OpenBSD the OS doesn't have ACL/XATTR so Bacula can't enable it there
> at all.

I'm seeing lots of:

Compiling verify_vol.c
"xacl.h", line 142: Warning: content hides XACL::content.
"xacl.h", line 168: Warning: content hides XACL::content.
"xacl.h", line 194: Warning: content hides XACL::content.


when compiling on Solaris 10.

Also in smaller quantities,

Compiling label.c
"label.c", line 490: Warning: jcr hides DCR::jcr.
"label.c", line 536: Warning: jcr hides DCR::jcr.
"label.c", line 573: Warning: jcr hides DCR::jcr.
3 Warning(s) detected.
Compiling lock.c
"lock.c", line 157: Warning: file hides DEVICE::file.
"lock.c", line 165: Warning: file hides DEVICE::file.
"lock.c", line 172: Warning: file hides DEVICE::file.
"lock.c", line 211: Warning: file hides DEVICE::file.
"lock.c", line 275: Warning: file hides DEVICE::file.
"lock.c", line 281: Warning: file hides DEVICE::file.
"lock.c", line 287: Warning: file hides DEVICE::file.
"lock.c", line 293: Warning: file hides DEVICE::file.
"lock.c", line 299: Warning: file hides DEVICE::file.
"lock.c", line 304: Warning: file hides DEVICE::file.
10 Warning(s) detected.


-- 
   Phil Stracchino
   Babylon Communications
   ph...@caerllewys.net
   p...@co.ordinate.org
   Landline: 603.293.8485

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to