Re: OBSD 4.0 + php5 ports (patch fails with systrace)

2007-01-29 Thread Otto Moerbeek
On Fri, 19 Jan 2007, Otto Moerbeek wrote: > > > It's systrace not capable of allocating mem for the args to > > > rename(2). The args are replaced by their canonical path (which is > > > absolute and thus quite long) and systrace uses the stackgap of 512 > > > bytes for that. Obviously two path n

Re: OBSD 4.0 + php5 ports (patch fails with systrace)

2007-01-18 Thread Otto Moerbeek
On Thu, 18 Jan 2007, J.C. Roberts wrote: > Hi Otto, > > I'm working on arj/unarj ports for use with clamav, and I'm struggling > to regain all the things I've forgotten about C. ;-) While searching > the archives, I stumbled across this tread from a couple weeks ago but > I'm still wondering

Re: OBSD 4.0 + php5 ports (patch fails with systrace)

2007-01-18 Thread patrick ~
--- "J.C. Roberts" <[EMAIL PROTECTED]> wrote: > On Friday 22 December 2006 02:54, Otto Moerbeek wrote: > > > Judging from the amount of noise this post made > > > I'm guessing that either a) no one cared or b) I > > > didn't supply enough relevant info for anyone to > > > bother to chime in with

Re: OBSD 4.0 + php5 ports (patch fails with systrace)

2007-01-18 Thread J.C. Roberts
On Friday 22 December 2006 02:54, Otto Moerbeek wrote: > > Judging from the amount of noise this post made > > I'm guessing that either a) no one cared or b) I > > didn't supply enough relevant info for anyone to > > bother to chime in with a hint or a pointer. > > > > I don't know much about systr

Re: OBSD 4.0 + php5 ports (patch fails with systrace)

2006-12-23 Thread Otto Moerbeek
On Fri, 22 Dec 2006, Otto Moerbeek wrote: > The problem reduces too the rename(2) system call. > > create a deep path: > > $ mkdir $(jot -s '' -b d 200) > $ cd d* > $ mkdir $(jot -s '' -b d 100) > $ cd d* > $ touch foo > $ systrace -At mv foo bar > : $ [this is an incomplete error message] >

Re: OBSD 4.0 + php5 ports (patch fails with systrace)

2006-12-22 Thread Otto Moerbeek
On Fri, 22 Dec 2006, patrick ~ wrote: > Hi Otto, > > It is very late here, but thanks for your hint > about NAME_MAX. > > I've been looking at the systrace sources trying > to figure out how it works and if there would be > any obvious path len issues that would pop-out. > I couldn't find any.

Re: OBSD 4.0 + php5 ports (patch fails with systrace)

2006-12-22 Thread patrick ~
Hi Otto, It is very late here, but thanks for your hint about NAME_MAX. I've been looking at the systrace sources trying to figure out how it works and if there would be any obvious path len issues that would pop-out. I couldn't find any. I took your suggestion to try and find a simple(er) test-

Re: OBSD 4.0 + php5 ports (patch fails with systrace)

2006-12-22 Thread Otto Moerbeek
On Fri, 22 Dec 2006, patrick ~ wrote: > Judging from the amount of noise this post made > I'm guessing that either a) no one cared or b) I > didn't supply enough relevant info for anyone to > bother to chime in with a hint or a pointer. > > I don't know much about systrace to be able to > make

Re: OBSD 4.0 + php5 ports (patch fails with systrace)

2006-12-22 Thread patrick ~
Judging from the amount of noise this post made I'm guessing that either a) no one cared or b) I didn't supply enough relevant info for anyone to bother to chime in with a hint or a pointer. I don't know much about systrace to be able to make any realistic progress with this, but some hints would