[I am trying to answer everybody who sent in their suggestions]
(to Wayne: the scripts runs OK outside cron; those messages are just
a couple of files which do not exist right now but may in the future: those
lines have never prevented the script from working).
(to Bernard Voelker: I did not try
On Fri, Oct 28, 2011 at 6:51 AM, Pedro Fortuny wrote:
> cp: ./Dropbox/HostMonsterPage/doc/ampliacion.pdf: No such file or directory
> cp: ./Dropbox/HostMonsterPage/doc/metodos.pdf: No such file or directory
>
I note that those are not rsync errors, so something is wrong with your
script. Did it
Pedro Fortuny wrote:
> I am running OS X Snow Leopard on the 'sender' side and
> Linux (2.6.32, possibly fedora but unsure) on the 'receiver'
> side. Both with rsync 3.0.9.
>
> If I run the following command from the command line:
>
> /usr/local/bin/rsync -av -e "ssh -i \
> /Users/pedrofor
Hi Pedro,
> Mmh, I put uname -a into the cron job and it says:
>
> core file size (blocks, -c) 0
> data seg size (kbytes, -d) unlimited
> file size (blocks, -f) unlimited
> max locked memory (kbytes, -l) unlimited
> max memory size (kbytes, -m) unli
Mmh, I put uname -a into the cron job and it says:
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It sounds like your cron jobs are memory limited. Can you put 'ulimit
- -a' into a cron job and see what it outputs?
On 10/28/11 09:51, Pedro Fortuny wrote:
> Hi,
>
> I am running OS X Snow Leopard on the 'sender' side and
> Linux (2.6.32, possibly
