This appears to be minor, but I'm posting it just to let you know
The first issue is that the installer tries to use wget, which is unfortunately not installed by Apple on OS X, so it fails. It is unclear whether the installer recovers by using curl (which *is* available on OS X), since subsequent messages suggest there was no problem, but nothing explicitly states what was done to recover from the lack of wget.
If it is recovering as it appears to be doing, it might be helpful to change the installer to say something like "using curl instead", or have it start by checking for wget rather than generating an error that users will see.
I'm not sure what causes the other errors, but the same is true with them: it would be helpful to know if they were recovered from successfully, rather than leaving us wondering if we have a defective installation of Litespeed.
Thanks!
The first issue is that the installer tries to use wget, which is unfortunately not installed by Apple on OS X, so it fails. It is unclear whether the installer recovers by using curl (which *is* available on OS X), since subsequent messages suggest there was no problem, but nothing explicitly states what was done to recover from the lack of wget.
Code:
Would you like to install AWStats Add-on module [y/N]? Y
/usr/local/bin/litespeed/admin/misc/awstats_install.sh: line 20: [COLOR="Red"]wget: command not found[/COLOR]
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1058k 100 1058k 0 0 319k 0 0:00:03 0:00:03 --:--:-- 377k
[COLOR="Red"]chown: root: Invalid argument[/COLOR]
/usr/local/bin/litespeed/admin/misc/awstats_install.sh: line 56: [COLOR="Red"]/usr/bin/test: No such file or directory[/COLOR]
[INFO] Creating a symbolic link from './awstats-6.6' to './awstats'
[OK] AWStats 6.6 has been successfully installed as a litespeed
add-on module.
Congratulations! The LiteSpeed Web Server has been successfully installed.
Command line script - "/usr/local/bin/litespeed/bin/lswsctrl"
can be used to start or stop the server.
I'm not sure what causes the other errors, but the same is true with them: it would be helpful to know if they were recovered from successfully, rather than leaving us wondering if we have a defective installation of Litespeed.
Thanks!