1415146333 Q * Ghislain1 Quit: Leaving.
1415149202 Q * fstd Remote host closed the connection
1415149243 J * fstd ~fstd@xdsl-87-78-184-11.netcologne.de
1415149420 M * Bertl off to bed ... have a good one everyone!
1415149424 N * Bertl Bertl_zZ
1415150938 Q * AndrewLe1 Ping timeout: 480 seconds
1415151763 Q * FireEgl Quit: Leaving...
1415153061 J * AndrewLee ~andrew@210.240.39.201
1415165968 N * Bertl_zZ Bertl_oO
1415169085 J * Ghislain ~aqueos@adsl1.aqueos.com
1415169583 Q * geos_one Quit: ChatZilla 0.9.91 [Firefox 33.0/20141016201439]
1415178712 Q * Romster Quit: Geeks shall inherit properties and methods of object earth.
1415179003 J * Romster ~Romster@202.168.100.149.dynamic.rev.eftel.com
1415182149 J * BenG ~BenG@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net
1415185080 M * theocrite When I try a vapt-get --all, I get the following message "vapt-get failed on vserver '$SERVER' with errorcode 1" for every stopped server.
1415185105 M * theocrite Shouldn't vapt-get silently replace --all by --running?
1415185224 M * theocrite ie add "(--all)         vsomething_opts=( "${vsomething_opts[@]}" "--running" );;" after the --quiet line in https://github.com/linux-vserver/util-vserver/blob/a042f226f3f58613a1ff200c1cc775c4352c6213/scripts/vapt-get ?
1415185368 A * theocrite will write a patch and ask for a merge
1415186824 M * theocrite Ok we can already use --running and it's handled by getAllVserversByArg
1415187825 M * theocrite Ok so here is the pull request: https://github.com/linux-vserver/util-vserver/pull/11
1415187911 M * theocrite daniel_hozac:  ↑ 
1415187989 J * gamingrobot_ sid10990@id-10990.highgate.irccloud.com
1415188099 J * _are__ ~quassel@h1417489.stratoserver.net
1415188153 Q * gamingrobot Ping timeout: 480 seconds
1415188153 N * gamingrobot_ gamingrobot
1415188179 Q * _are_ Read error: Connection reset by peer
1415189523 Q * Aiken Remote host closed the connection
1415190810 Q * hlew_ Read error: Connection reset by peer
1415190842 J * hlew ~hlew@173-164-198-18-SFBA.hfc.comcastbusiness.net
1415191641 M * Ghislain theocrite: hum yes for vapt-get that could do it, --running was added afterward so this explain it
1415192401 Q * fstd Remote host closed the connection
1415192442 J * fstd ~fstd@xdsl-87-78-184-124.netcologne.de
1415192907 Q * BenG Quit: I Leave
1415193533 M * theocrite Ghislain: I see. Thanks.
1415193547 M * theocrite Ghislain: So do you think my patch is relevant?
1415193607 M * Ghislain yes it is it's an improvement to vsomethign that was not  ported to the tools so this is a good idea
1415207200 J * bonbons ~bonbons@2001:a18:201:5a01:dd95:5f66:8165:66a3
1415220083 J * Aiken ~Aiken@d63f.h.jbmb.net
1415220670 Q * hlew 
1415222738 J * hlew ~hlew@173-164-198-18-SFBA.hfc.comcastbusiness.net
1415223832 Q * bonbons Quit: Leaving
1415224197 M * hlew Hey there. I'm looking for some insight on the oom killer. I've seen behavior similar to what was described as the oom killer killing processes in multiple guests at the same time.
1415224202 M * hlew http://irc.13thfloor.at/LOG/2006-04/LOG_2006-04-19.txt
1415224258 M * hlew "1145466831 M * kir Bertl, oom killer apparently kills random process -- not only in your guest but in other guests as well."
1415224291 M * hlew I'm also seeing this happen when testing memory limitations.
1415224684 J * CcxCZ ~ccxCZ@asterix.te2000.cz
1415224799 M * CcxCZ are there any plans to make a grsec/pax-enabled patchset?
1415228823 Q * Ghislain Quit: Leaving.