C. Bensend wrote on Tue, Feb 23, 2010 at 03:23:47PM -0600: > Ingo Schwarze wrote: >> C. Bensend wrote on Tue, Feb 23, 2010 at 02:42:34PM -0600:
>>> I'm running into some problems with my home backup server. It >>> uses rsnapshot to grab backups from multiple hosts several times >>> a day, and saves them to dual 1.5TB drives. >>> >>> Recently, I've begun getting rsnapshot failures, such as this >>> one: >>> >>> ERROR: out of memory in receive_sums [sender] >> Probably not related to ports, but "out of memory" often means that >> you are hitting a memory limit, not that you are running out of >> physical memory (and swap). >> >> Did you already look at the ulimit builtin command in ksh(1)? [...] > I had thought about limits, but this particular process runs as > root and should therefore be relatively unhindered... root is not exempt from process limits, even though the defaults are higher, see login.conf(5). [...] > An interesting point you mention - ksh - I don't run that as > root's shell. I might try switching it for tonight's run just > to see if behavior changes. That probably won't help. Limits do not depend on which shell you are using. Only the command to change limits depends on which shell you are using. So, in case your process is really needing lots of memory and hitting the limit, changing the limit might help, using the apropriate command in whatever shell you are using - for example, builtin "limit" in csh(1). On the other hand, in case your problem is that something is massively leaking memory (or some other bug causing the message), then raising the limit may not help.
