Re: httpd syscall 72

2015-10-07 Thread Scott Vanderbilt
On 10/7/2015 12:38 PM, Daniel Jakots wrote: On Wed, 7 Oct 2015 12:18:32 -0700, Scott Vanderbilt wrote: Might anyone have an idea where I can start to look for the problem? semarie@ explained how to debug/report tame(2) problem :

Re: httpd syscall 72

2015-10-07 Thread Theo de Raadt
> The syscall (72) maps to SYS_kevent 72. Someone uses tame "malloc" instead of tame "stdio".

Re: httpd syscall 72

2015-10-07 Thread Adam Wolk
On Wed, 7 Oct 2015 12:18:32 -0700 Scott Vanderbilt wrote: > Running latest snapshot (amd64), I get a 'sycall 72' message when > attempting to start httpd, e.g.: > > httpd(10043): syscall 72 > > I'm pretty sure this started with snapshots after Sept. 27. > > Might

Re: httpd syscall 72

2015-10-07 Thread Rob Pierce
>From Stuart in response to a previous inquiry: Rob > >> If you need a working version, the diffs aren't committed yet, so you can > >> rebuild httpd from source and it should work fine. > >> > > Thanks for the info Ted. I'm currently rebuilding the src, following the > > "5 - Building the

httpd syscall 72

2015-10-07 Thread Scott Vanderbilt
Running latest snapshot (amd64), I get a 'sycall 72' message when attempting to start httpd, e.g.: httpd(10043): syscall 72 I'm pretty sure this started with snapshots after Sept. 27. Might anyone have an idea where I can start to look for the problem? Thanks. # /etc/rc.d/httpd start