It fixed! When I make shell script and send to some file like:
/usr/local/backupscripts/bk.sh > /var/log/rmsupdate.log
and inside bk.sh I have the same command as it was in cron:
su -l postgres -c "/bin/gunzip -c /backup/rms.gz |
/usr/lib/postgresql/8.2/bin/psql rms"
Only putting command in she
The usual trap in cron usage is the fact that crontab commands are executed
in a cleanroom environment, ie no environment variable is used/inherited, so
PATH, HOME, PGDATA, etc are not set/available when the command is launched.
You can set vars or be very explicit in your script including DB name
> same result when it running trough cronjob. Manually everything is
> fine. Even I put this commands (without su -l ...) in postgres user
> crontab, but same result.
>
> Server is ubuntu 64bit. Does it makes any difference from 32bit in
> terms of crontab functionality?
System architecture shoul
