1) AFAIK /etc/php/apache2/php.ini applies to PHP via Apache (i.e. as it applies to the Web side of SugarCRM) and /etc/php/cli/php.ini applies to PHP run from the commandline (e.g. when run manually from the commandline or via a cron job). IIRC often one is a symlink to the other (although it sounds like that is not the case in this instance).
2) Assuming that you want to run PHP from the commandline then yes (see above for why). I am not familiar with SugarCRM specifically but from my experience many PHP webapps use cron jobs to do background processing so I imagine that it would be neccessary.
3) see 1 above
4) see 1 above (Often web apps use cron jobs to run tasks in the back ground).
5) AFAIK you could rename /etc/php/cli/php.ini (as a precautionary step) and in it's place create a symlink to /etc/php/apache2/php.ini
Also note that because of the nature of the different way PHP runs within the web server vs from the commandline, changes to /etc/php/apache2/php.ini are not applied until Apache is restarted, whereas any new PHP instances started after changes to /etc/php/cli/php.ini should apply immediately.
I'm not completely sure
So don't take this as gospel... but:
1) AFAIK /etc/php/apache2/php.ini applies to PHP via Apache (i.e. as it applies to the Web side of SugarCRM) and /etc/php/cli/php.ini applies to PHP run from the commandline (e.g. when run manually from the commandline or via a cron job). IIRC often one is a symlink to the other (although it sounds like that is not the case in this instance).
2) Assuming that you want to run PHP from the commandline then yes (see above for why). I am not familiar with SugarCRM specifically but from my experience many PHP webapps use cron jobs to do background processing so I imagine that it would be neccessary.
3) see 1 above
4) see 1 above (Often web apps use cron jobs to run tasks in the back ground).
5) AFAIK you could rename /etc/php/cli/php.ini (as a precautionary step) and in it's place create a symlink to /etc/php/apache2/php.ini
Also note that because of the nature of the different way PHP runs within the web server vs from the commandline, changes to /etc/php/apache2/php.ini are not applied until Apache is restarted, whereas any new PHP instances started after changes to /etc/php/cli/php.ini should apply immediately.