you're right. it was my mistake. i didn't apply the patch, but added the changes manually. i probably overlooked the "2>". sorry for that. ;) alex Juergen Lock schrieb am 2009-07-01: > In article > <permail-2009070119081980e26a0b000048ca-a_best01_at_message-id.uni-muenster.de> > you write: > >the latest patch to get rid of the ulimit warning doesn't suppress > >the warning > >since it get's output to stderr and not to stdout. replacing it with > >"ulimit > >-s 32768 2 > /dev/null 2>&1" should work. > You mean the patch doesn't work for you? It already does redirect > stderr to /dev/null (`2>/dev/null'), which works as expected when > tested here from commandline /bin/sh and from a script, and also when > invoking firefox after ulimit -s 16384. If it doesn't work for you > there > must be something else going on... > Wondering... > JuergenReceived on Wed Jul 01 2009 - 17:50:42 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:51 UTC