Jack L. Stone wrote:

> At 12:56 PM 6/16/2011 -0400, Michael Powell wrote:
>>Jack L. Stone wrote:
>>
>>The no-accf.conf under includes is for if you do not desire to use either
>>of
>>the AcceptFilter choices, one for httpd the other for SSL traffic.  These
>>can be loaded as kernel modules in /boot/loader.conf as such:
>>
>>accf_http_load="YES"
>>accf_data_load="YES"
>>
>> Mike
> 
> Mike:
> 
> Got the apache22 configured on the test server with one exception being
> the error I keep getting regarding this one:
> 
> "[warn] (22)Invalid argument: Failed to enable the 'httpready' Accept
> Filter"
> 
> I first loaded it in the kernel via kldload:
> # kldload accf_http
> 
> The first apache22 restart didn't have the error, but returned on other
> restarts. Can't seem to unload the line from the kernel and add to the
> boot loader.conf. What did I do wrong?
> 
The /boot/loader.conf is just a text file that you add lines of text. It is 
read and stuff done only at boot. When these modules are loaded at boot you 
do not need to kldload them. Nearest thing I can figure is they need to be 
loaded at boot, then Apache gets started right after. When this sequence 
applies there will not be these messages. For a server that stays up and 
online all the time this is not a problem. The only time I've ever seen this 
error is on apachectl restarts at times other than booting. And I don't 
really know why either. 

Strictly speaking these thing are not required, they are only supposedly 
some small performance enhancer. I have also never seen Apache actually fail 
or exhibit any problems even in spite of this error message. But I don't 
apachectl restart (or reboot for that matter) very often.  You could just as 
easily forgo this, e.g. not load the kernel modules and leave the 
Include etc/apache22/Includes/*.conf line in your httpd.conf and never 
notice any difference. This will load the no-accf.conf files from the 
includes directory and tell Apache not to look for these modules. 

Whether and/or how much these actually help Apache is probably debatable. 
They are supposed to be helpful performance-wise, but as to how much I 
couldn't say. But I have never seen this error/warning message actually be 
related to any problem, and since I don't reboot or restart all the time I 
don't get them. You could just as easily forego using them and probably 
never notice.

-Mike



_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to