>> $ ulimit -S -f 3300 >> $ rsync --quiet --partial >> ftp.es.debian.org::debian-cd/3.0_r4/alpha/debian-30r4-alpha-binary-1.iso . >> rsync: connection unexpectedly closed (53 bytes received so far) [generator] >> rsync error: error in rsync protocol data stream (code 12) at io.c(359) >> >> rsync dumps core and leaves an incomplete downloaded file whose name >> begins with a dot. Since the --partial option is used, it should rename >> it to the target file, and obviously should not dump core and print an >> error. > >The "problem" here is that the ulimit causes a signal to be sent to the >process, which causes the core dump.
Well, it is a real problem, why do you use quotes? Any core dump in any program is a bug. >If I stop the rsync before that by hitting ctrl-C, the tmpfile is >correctly renamed before the process exits. Presumably the SIGXFSZ >should be trapped... That's curious. I did not even know about this signal. I wonder why dumping core is the default behaviour. Maybe this is what has changed but, if this is the case, this problem should affect most programs around there. Very strange. >Does your script actually set the filesize ulimit? Yes. And it has worked for four years, from mid 2000 to April, 2004. As I wrote at the beginning of my report, I have not used it since then, so I cannot be more precise as far as the date of change is concerned. >If so, how is the iso ever to be downloaded? I only need the first few kilobytes, and that is the simplest way I found to do it from a shell script. It worked reliably. In fact, it still works, if after the core dump I rename the hidden partial file to the target file name: that's what I'm doing, as a temporary workaround. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
