I was getting this too.. and had a play around on my development server and production server.
Production server went fine with the above commands..
but I could not get
sudo apt-get install ghostscript
To run in terminal using WinSCP.. seems to hang.. does give me this output..
but with this in mind when the
sudo su daemon -s /bin/sh -c
I get a clean output.. so not to worry about that.. just a note for others..
But on the production server.. when I run this command I get an error..
So it seems that that last line is hanging the CRON job ..
I went another way and using an external cron manager
as per Moodle cron documents..
and have had it run every 5 mins for the last half an hour and seems to be working fine..
so this is one way to handle this..
Probably my question is what does the bitnami team feel is a good timing to run this..
The Moodle Documents are saying run cron every minute, but that seems a bit excessive to me..
"The Moodle 'cron' process is a PHP script (part of the standard Moodle installation) that must be run regularly in the background. The Moodle cron script runs different tasks at differently scheduled intervals.
IMPORTANT: Do not skip setting up the cron process on your server for your Moodle. Your site will not work properly without it.
It is recommended that the cron is run every minute, as required for asynchronous activity deletion when using the recycle bin."
Would every few hours be fine?
once every 24 hours?
What would you suggest?