Strange bug (buffer overflow) happening only under cron
Henri Shustak
henri.shustak at gmail.com
Sun Oct 30 19:35:41 MDT 2011
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) unlimited
> open files (-n) 2560
> pipe size (512 bytes, -p) 1
> stack size (kbytes, -s) 8192
> cpu time (seconds, -t) unlimited
> max user processes (-u) 266
> virtual memory (kbytes, -v) unlimited
>
> which is the same (exactly) as the output when run from
> the shell (bash, by the way, in both environments).
>
> Thanks, anyway.
Have you tried using LaunchD as you are scheduling from Mac OS X?
-----------------------------------
This email is protected by LBackup
http://www.lbackup.org
More information about the rsync
mailing list