ftasv and ScoreBoardFile on FreeBSD 10 with jails

[Benjamin Connelly]

We recently upgraded some FreeBSD 9.1 servers to FreeBSD 10.1 and found 
it broke the scoreboard viewing utility we were using, the "ftasv" port 
(ftss).

For that tool to work apache is supposed to be configured to use 'a 
"name based" shared memory segment' (from their README) by the directive

  ScoreBoardFile /var/run/apache_status

That used to (on FreeBSD 9.1) create that "file". Then we could execute 
'ftasv /var/run/apache_status' to interpret it and see what requests 
apache was working to serve.

This even worked with many different apache instances running each in 
their own jail, where all the jails actually share the same basejail 
/usr/local/sbin/httpd binary. Inside each jail we could see just the 
requests that instance of apache was working on.

But after the FreeBSD upgrade to 10.1 we no longer see the apache_status 
file in the filesystem, and ftasv seems to actually report the most 
recent hits from the most recently restarted instance of apache, even if 
that's in another jail!? (On a system with no jails and just the one 
instance of apache, it's not actually a problem!)

Can anybody point me toward the right dials to turn if it's still 
possible to do this scoreboard viewing of each independent apache 
instance? (Like I think I may need security.jail.param.allow.sysvipc=1 
in the jails, but I'm also finding with ezjail I'm not actually able to 
get that set because it's creating the /var/run/jail.JAILNAME.conf file 
with both these lines in it:
         allow.sysvipc = 0;
         allow.sysvipc=1;


  Ben