Try by below method:
30 09 * * * sh /autopgdump.sh
These should work.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Cronjob-to-autobackup-database-tp5734873p5735118.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin
so if i putting the .SH files under root directory
the cronjob will look similar like
30 09 * * * /root/autopgdump.sh
please advice?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Cronjob-to-autobackup-database-tp5734873p5735088.html
Sent from the PostgreSQL - admin m
Hi all,
I'm currently performing a hash check for password verification.I'm
generating an md5 hash or checking for plain text in pg_shadow. However,
outside of these two "out-of-the-box" options, what if someone is using
pg-crypto or any other PAM ? How can I differentiate between say md
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 cro
Here is a crontab example. I always specify the absolute path.
0 0 * * * /postgresql/home/scripts/backup/backup_wal_enabled_instance.sh
inst1 5432
Peter Krawetzky
-Original Message-
From: [email protected]
[mailto:[email protected]] On Behalf Of tey
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 director