Re: ENOMEM on socket writes

Hello! > memory". Rsync is writing on a socket which is set non-blocking and > the write is apparently returning ENOMEM. This must not happen with stock 2.4.0. TCP never returns ENOMEM. Please, investigate. But application should be ready to get this error yet. > >From the point of view of t

ENOMEM on socket writes

Using 2.4, and the prereleases since about early December or so, I have been seeing rsync dying with an error "write: unable to allocate memory". Rsync is writing on a socket which is set non-blocking and the write is apparently returning ENOMEM. Is this actually a new behaviour, or just somethi