| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Allen <dba(at)girders(dot)org> |
| Cc: | v(dot)demartino2(at)virgilio(dot)it, postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: cron & backup |
| Date: | 2005-01-19 11:03:17 |
| Message-ID: | 20050119110312.GB18648@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jan 18, 2005 at 06:30:32PM -0500, Allen wrote:
> I had a problem in the past with the vaccumdb command on 7.2.3
> mysteriously never returning when run from cron on FreeBSD, but it ran
> fine from cmdline. Had to be an environmental issue. Not having time to
> track it down, I tried an alternative lazy method...
>
> /usr/local/bin/vacuumdb -z -f dbname <-- sometimes never returned
If it never returned it would still be running right. So it should show
up when you run "ps". You would be able to strace to see what the
problem was. Note, if a script has no output you don't get an email
either.
Hope this helps,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2005-01-19 11:03:52 | Re: Postgres crashed when adding a sequence column |
| Previous Message | Martijn van Oosterhout | 2005-01-19 10:59:37 | Re: Multiline plpython procedure |