You can debug what's going wrong with the script by adding this:
30 09 * * * /autopgdump.sh &> /autopgdump.log
that will write the output of the command to a logfile living at /autopgdump.log. If there's anything wrong with your
environment(something not in the PATH of the user running the cron, etc) it should be written there. Cron runs with a
slightlydifferent environment than a regular login shell, so this can help you figure out exactly what's going wrong.
note: each time cron executes that script, it will replace the contents of /autopgdump.log; not append to it.
Also, just to double check, the above configuration would run the script at 9:30am every day, so did you wait until
9:30for the script to run?
...spike
On Dec 3, 2012, at 8:13 PM, teyking2003 wrote:
> i have a cronjob setting up as below
> 1)Command crontab -e
> 2)Keyin 30 09 * * * /autopgdump.sh
> 3) Save to new crontab file.
> but nothing happen, the backup process won't start.
>
> i manage to perform manual backup by running the following command
> sudo ./autopgdump.sh( SH file store under root directory
>
> looking for the correct ways to setting up the cronjob.
>
> thanks
>
>
>
> --
> View this message in context: http://postgresql.1045698.n5.nabble.com/Cronjob-to-autobackup-database-tp5734873.html
> Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin