On 2012/02/29 17:32, Antoine Jacoutot wrote: > On Wed, Feb 29, 2012 at 04:28:36PM +0000, Stuart Henderson wrote: > > On 2012/02/29 17:03, David Coppa wrote: > > > On Wed, Feb 29, 2012 at 4:43 PM, Antoine Jacoutot > > > <[email protected]> wrote: > > > > CVSROOT: /cvs > > > > Module name: ports > > > > Changes by: [email protected] 2012/02/29 08:43:16 > > > > > > > > Modified files: > > > > net/avahi : Makefile > > > > > > > > Log message: > > > > Add NO_SYSTRACE for now, otherwise gtar fails in mysterious way because > > > > systrace(1) will prevent native-linkat. > > > > Reported by Juan Francisco Cantero Hurtado. > > > > > > > > > > I have the same issue with tomcat: > > > > > > systrace: deny user: dcoppa, prog: /usr/local/bin/gtar, pid: > > > 14062(0)[22633], policy: /usr/bin/make, filters: 241, syscall: > > > native-fchmodat(314) > > > /usr/local/bin/gtar: apache-tomcat-7.0.25/bin: Cannot change mode to > > > rwxr-xr-x: Operation not permitted > > > /usr/local/bin/gtar: Exiting with failure status due to previous errors > > > > > > > > > How should I proceed? NO_SYSTRACE for this too? > > > > > > ciao > > > David > > > > > > > Until/unless we can properly handle this in systrace, the simplest > > workaround is probably to disable linkat in gtar by passing flags to > > autoconf. > > I'm not sure we should remove support only because systrace is not able to > cope. But maybe it's just me.
Any idea if linkat gives any actual benefit for tar, or are they just using it because it's there? (And if it is useful, should pax make use of it too?)
