I already somewhat introduced this subject in a previous threads. I found several problems about current cronjobs starting server/cron_daily(.sh) and server/server(.sh): they are located in root's user crontab they needlessly call a shell script while the cronjob could call the PHP script directly This is the exact content of this crontab: Code: * * * * * /usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log 30 00 * * * /usr/local/ispconfig/server/cron_daily.sh > /dev/null 2>> /var/log/ispconfig/cron.log About 1., I think I saw in the code that it was editing directly /var/spool/cron/crontabs/root. That should really be avoided as the crontab utility does some validation and notifies the cron daemon about a modification. Anyway, I'm not just suggesting to use a pipe to crontab to add it, but rather to create a new /etc/cron.d/ispconfig file with this same content. About 2., other than starting the PHP script, the current shell scripts are just loading a specific content for the PATH environment variable and (for only one) loading /etc/profile. Even writing to the log file is done from the crontab. I'm pretty sure the PATH is really needed anywhere from within those PHP scripts (as every utility called should be with its full access path). On Debian Lenny at least, this /etc/profile is almost empty, only setting things like the PATH (again) and some shell CLI usability (obviously not needed). I can't imagine what else could be read from /etc/profile which should be used from within those scripts. I guess that just replacing the calls to something like this would work without problem. Code: * * * * * /usr/bin/php /usr/local/ispconfig/server/server.php > /dev/null 2>> /var/log/ispconfig/cron.log 30 00 * * * /usr/bin/php /usr/local/ispconfig/server/cron_daily.php > /dev/null 2>> /var/log/ispconfig/cron.log We are going to test that in the next days.