Hello,
found an interesting difference between include behaviour of apache 2.2
and 2.4
Have an include in apache2.conf:
Include /etc/apache2/conf.d/
When editing a conf file in this folder by vi, vi creates a new swp file.
lets say i edit a file logging.conf, so vi creates a file .logging.conf.swp
When running "apachectl configtest" at this particular time, apache 2.4
tries to include the .logging.conf.swp which fails, because
.logging.conf.swp is binary and invalid.
This prevents apache 2.4 from sucessfully start and leads to downtime.
Apache 2.2 tries not to include this .swp file and restarts
successfully. Include is the same as above. (Include /etc/apache2/conf.d/)
A quick fix could be to include only *.conf files:
Include /etc/apache2/conf.d/*.conf
But i wonder if apache should basically tries to include a file
"beginning with dot"/"ending with swp" which generelly indicates a
temporary/hidden file.
In my opinion include behaviour of apache 2.2 was more practice-oriented.
Thanks,
Hajo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
