ENOMEM on socket writes

[Paul Mackerras]

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 something which was possible
all along but which has been made more likely by the recent VM
changes?

deal with constructively.  Select will say that the socket is
writable, so there doesn't seem to be a good way of waiting until the
write has a chance of succeeding.  About the only thing that I can see
to do is just to spin trying the write over and over - does anyone
have a better idea?

Paul.

-- 
Paul Mackerras, Open Source Research Fellow, Linuxcare, Inc.
[phone] tel, [phone] fax
[e-mail], http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.