[prev in list] [next in list] [prev in thread] [next in thread]
List: openbsd-vax
Subject: Re: rsync failures - possible ulimit issues?
From: "Jim MacKenzie" <jim () photojim ! ca>
Date: 2009-08-24 16:15:08
Message-ID: 24FAB1B55500432F8EFB654304086279 () JIMM
[Download RAW message or body]
----- Original Message -----
From: "Tobias Ulmer" <tobiasu@tmux.org>
To: "Jim MacKenzie" <jim@photojim.ca>
Cc: <vax@openbsd.org>
Sent: Saturday, August 22, 2009 3:28 AM
Subject: Re: rsync failures - possible ulimit issues?
> MAXDSIZ in /usr/src/sys/arch/vax/include/vmparam.h is limited to 32MB.
> You could try to increase that limit, either by editing the header or with
> a new kernel configuration.
> Of course all kinds of bad things may happen...
I tried exactly that (by editing the header and recompiling).
I invoked my rsync script and it worked... for a long time (much further
than it did previously). But I did eventually get a kernel panic.
My instinct at this point is to file a bug report for rsync, because it
clearly does not work reliably with 32 MB of data space and obviously we
have at least one platform that is limited to that amount.
My other instinct is to try a different kernel header setting (perhaps 48MB)
and see if that is more reliable.
I was going to do a kernel build if rsync succeeded, to test the kernel
reliability, but that is obviously of no benefit with my existing machine
state. :)
If you (or anyone else on the list) have any other suggestions of things I
can try (both to help my situation and to provide useful information for the
developers), please let me know.
Jim
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic