On Friday 07 June 2002 02:33, Nathan Scott wrote:
> hi Mark,
>
> On Thu, Jun 06, 2002 at 12:19:47PM +0100, mark wrote:
> > acl_free(0x0805476c, 32768, 0x0805476c, 0, 0xbffff6a4) = 0
> > acl_get_file(0xbffffce0, 16384, 0x0805476c, 0, 0xbffff6a4) = 0x08054784
> > acl_set_file(0x08054710, 16384, 0x08054784, 0, 0xbffff6a4) = -1
> > __ctype_get_mb_cur_max(256, 0x08054140, 0, 0x4002a180, 0x4002b574) = 1
> > dcgettext(0, 0x0805294a, 5, 0x4009fb14, 0) = 0x0805294a
> > dcgettext(0, 0x0805294c, 5, 0x0804f01f, 0) = 0x0805294c
> > dcgettext(0, 0x08052606, 5, 0xbffff68c, 0x08054140) = 0x08052606
> > __errno_location() = 0x40157c20
> > error(0, 22, 0x08052606, 0x08054140, 0x08054710cp: preserving permissions
> > for `/home/usr/local/share/doc': Invalid argument
> > ) = 0
>
> OK, I know what is happening here now - it seems to me that libacl
> is doing some unholy things, including attempting to set default
> ACLs with no ACEs. We will change XFS to be more graceful in the
> presense of this condition, and take this up with the libacl and
> fileutils patch author.
>
> Thanks for reporting and helping resolve the problem. The fix to
> prevent these warning messages will show up in XFS CVS shortly.
>
> cheers.
No problem. Thanks for the help and feedback.
Mark
|