Re: apache - (34)Result too large or too small

[Sarton O'Brien <bsd-xen%roguewrt.org@localhost>]

Sarton O'Brien wrote:
> Mihai Chelaru wrote:
> > Can you check exactly what fails with ERANGE ? Is it a semctl call ?
>
> I'm a complete noob so if this isn't what you were after, you might have 
> to do a bit of hand holding:

Yep, noobin it up alright. I think this is the bit I should have sent:

11719      1 httpd    RET   read 2500/0x9c4
 11719      1 httpd    CALL  read(0x22,0x7f7ffbf790a8,0x1000)
 11719      1 httpd    GIO   fd 34 read 0 bytes
       ""
 11719      1 httpd    RET   read 0
 11719      1 httpd    CALL  close(0x22)
 11719      1 httpd    RET   close 0
 11719      1 httpd    CALL  semget(0,1,0x380)
 11719      1 httpd    RET   semget 262144/0x40000
 11719      1 httpd    CALL  ____semctl50(0x40000,0,8,0x7f7fffffd5b0)
 11719      1 httpd    RET   ____semctl50 -1 errno 34 Result too large 
or too small
 11719      1 httpd    CALL  ____semctl50(0x40000,0,0,0x7f7fffffd5a0)
 11719      1 httpd    RET   ____semctl50 0
 11719      1 httpd    CALL  __gettimeofday50(0x7f7fffff9520,0)
 11719      1 httpd    RET   __gettimeofday50 0
 11719      1 httpd    CALL  access(0x7f7ffc4ea08f,4)
 11719      1 httpd    NAMI  "/etc/localtime"
 11719      1 httpd    RET   access 0
 11719      1 httpd    CALL  open(0x7f7ffc4ea08f,0,0)
 11719      1 httpd    NAMI  "/etc/localtime"
 11719      1 httpd    RET   open 34/0x22
 11719      1 httpd    CALL  read(0x22,0x7f7fffff6a60,0x249c)
 11719      1 httpd    GIO   fd 34 read 785 bytes

Sarton