On Tue, Feb 02, 2010 at 09:32:43PM +0100, Ingo Schwarze wrote:
Antti Harri wrote on Tue, Feb 02, 2010 at 07:31:57PM +0200:
xargs' -L switch isn't working when using -0 flag.
After checking POSIX.1 (2008), i conclude that our implementation and
manual are correct in this respect. The -L
On Thu, Feb 04, 2010 at 11:51:11AM +0500, Anton Maksimenkov wrote:
2010/2/3 Ariane van der Steldt ari...@stack.nl:
On Tue, Feb 02, 2010 at 01:21:55AM +0500, Anton Maksimenkov wrote:
uvm_map_lookup_entry()... in uvm_map_findspace()...
I'm pretty sure that function is bugged: I think it
2010/2/3 Owain Ainsworth zer...@googlemail.com:
...you can't just go straight to the start of the map.
Say i386 where W^X is done using segments. if you dump
something right at the other end of the segment, that pretty much screws
it. Perhaps going back to the min hint for the protection and
On Thu, Feb 4, 2010 at 2:48 AM, Atte Peltomdki atte.peltom...@iki.fi wrote:
On Tue, Feb 02, 2010 at 09:32:43PM +0100, Ingo Schwarze wrote:
Antti Harri wrote on Tue, Feb 02, 2010 at 07:31:57PM +0200:
xargs' -L switch isn't working when using -0 flag.
After checking POSIX.1 (2008), i conclude
On Thu, Feb 04, 2010 at 09:29:13AM -0700, Jeff Ross wrote:
Jeff Ross wrote:
On Sat, 30 Jan 2010, Bob Beck wrote:
Ooooh. nice one. Obviously ami couldn't get memory mappings and
freaked out.
While not completely necessary, I'd love for you to file that whole
thing into sendbug()
On Thu, Feb 4, 2010 at 2:21 PM, Jeff Ross jr...@openvistas.net wrote:
kern.shminfo.shmall=512000
kern.shminfo.shmmax=76800
Oh, when I said it was safe to crank shmmax I didn't know you'd be
setting the bufcache to huge numbers too. ;)
available memory in the server. I tried setting mine
Hi Atte,
Atte Peltomdki wrote on Thu, Feb 04, 2010 at 12:48:47PM +0200:
On Tue, Feb 02, 2010 at 09:32:43PM +0100, Ingo Schwarze wrote:
Antti Harri wrote on Tue, Feb 02, 2010 at 07:31:57PM +0200:
xargs' -L switch isn't working when using -0 flag.
After checking POSIX.1 (2008), i conclude
2010/2/5 Ted Unangst ted.unan...@gmail.com:
On Thu, Feb 4, 2010 at 2:21 PM, Jeff Ross jr...@openvistas.net wrote:
kern.shminfo.shmall=512000
kern.shminfo.shmmax=76800
Oh, when I said it was safe to crank shmmax I didn't know you'd be
setting the bufcache to huge numbers too. ;)
2010/2/5 Anton Maksimenkov anton...@gmail.com:
set chared buffers to something not so big... say, 256Mb or so (I just
I misprint. Of course it's shared, not chared. Sorry.
--
antonvm
