i was thinking too, why the include_shell was in place, but did not
bother to look to git history.
digged now, and no obvious reason written. so i guess the glob include
didn't exist at the time
https://github.com/pld-linux/lighttpd/commit/4ea50529e182703e064e0053d13c9e7953f0d201
Yes, glob
On 9/18/18 11:12 AM, Marcin Krol wrote:
On 18-Sep-18 09:23, glen wrote:
the same host, updated
wintersunset /etc/lighttpd # rpm -q glibc lighttpd; ls -l
/etc/lighttpd/vhosts.d/
glibc-2.28-3.x86_64
lighttpd-1.4.50-2.x86_64
total 0
wintersunset /etc/lighttpd #
so it's lighttpd behavior
On 18-Sep-18 09:23, glen wrote:
the same host, updated
wintersunset /etc/lighttpd # rpm -q glibc lighttpd; ls -l
/etc/lighttpd/vhosts.d/
glibc-2.28-3.x86_64
lighttpd-1.4.50-2.x86_64
total 0
wintersunset /etc/lighttpd #
so it's lighttpd behavior change.
Since 1.4.50 include_shell behavior
the same host, updated
wintersunset /etc/lighttpd # rpm -q glibc lighttpd; ls -l
/etc/lighttpd/vhosts.d/
glibc-2.28-3.x86_64
lighttpd-1.4.50-2.x86_64
total 0
wintersunset /etc/lighttpd #
so it's lighttpd behavior change.
On 9/18/18 9:15 AM, Elan Ruusamäe wrote:
on some other system, empty
on some other system, empty vhosts.d does not result such error as on carme:
wintersunset lighttpd/vhosts.d # rpm -q glibc lighttpd; ls -l
/etc/lighttpd/vhosts.d/
glibc-2.28-3.x86_64
lighttpd-1.4.49-3.x86_64
total 0
wintersunset lighttpd/vhosts.d # grep vhosts.d /etc/lighttpd/lighttpd.conf
On 17/09/2018 11:53, Arkadiusz Miśkiewicz wrote:
On 17/09/2018 00:24, Elan Ruusamäe wrote:
poldek:/all-avail> !sh -c '/sbin/service lighttpd configtest'
Checking Lighttpd Web Server
On 17/09/2018 00:24, Elan Ruusamäe wrote:
poldek:/all-avail> !sh -c '/sbin/service lighttpd configtest'
Checking Lighttpd Web Server
configuration[
FAIL ]
2018-09-17
