1338338065 M * puck Is it possible to have a different clock inside a vserver? (i.e., GMT is different) 1338338079 M * puck (General looking around says: no) 1338340142 Q * fisted_ Quit: brb 1338340485 M * Bertl yes, you can do that, it's called virt time 1338340501 M * Bertl but usually you just want to adjust the timezone 1338341188 Q * nyerup Quit: Bye. 1338343779 M * Bertl off to bed now ... have a good one everyone! 1338343785 N * Bertl Bertl_zZ 1338344653 J * fisted ~fisted@xdsl-87-78-180-88.netcologne.de 1338346544 Q * clopez Ping timeout: 480 seconds 1338347978 M * puck Bertl_zZ: ahhh, cool. Thank you 1338352589 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f 1338352683 J * fisted_ ~fisted@xdsl-81-173-188-161.netcologne.de 1338352781 Q * FireEgl Remote host closed the connection 1338353098 Q * fisted Ping timeout: 480 seconds 1338353738 J * FireEgl FireEgl@2001:470:e5ad:1:28e1:7106:fd44:bb40 1338355061 J * ghislain ~AQUEOS@adsl2.aqueos.com 1338357740 J * nyerup irc@jespernyerup.dk 1338358653 J * ncopa ~ncopa@3.203.202.84.customer.cdi.no 1338363587 J * arthus ~arthus@reverse-232.fdn.fr 1338364479 J * petzsch ~markus@dslb-094-222-100-245.pools.arcor-ip.net 1338366085 J * kir ~kir@swsoft-msk-nat.sw.ru 1338367153 J * Walex ~Walex@client-7-205.eduroam.oxuni.org.uk 1338370753 J * clopez ~clopez@fanzine.igalia.com 1338370765 J * BenG ~bengreen@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com 1338371979 J * disposab1e disposable@shell.websupport.sk 1338372158 Q * disposable Ping timeout: 480 seconds 1338373138 N * Bertl_zZ Bertl 1338373148 M * Bertl morning folks! 1338375021 M * Bertl off for now ... bbl 1338375025 N * Bertl Bertl_oO 1338377255 Q * Aiken Remote host closed the connection 1338377947 Q * hijacker Read error: Connection reset by peer 1338377947 J * hijacker_ ~hijacker@213.91.163.5 1338382975 P * kir PING 1338382975 1338385387 Q * BenG Quit: I Leave 1338385902 J * BenG ~bengreen@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com 1338387187 Q * bergerx Ping timeout: 480 seconds 1338387290 J * bergerx ~bergerx@46.196.253.84 1338389658 J * dowdle ~dowdle@scott.coe.montana.edu 1338389998 Q * ensc Ping timeout: 480 seconds 1338392602 Q * petzsch Read error: Connection reset by peer 1338392777 Q * dowdle Remote host closed the connection 1338393975 J * bonbons ~bonbons@2001:960:7ab:0:34bb:5970:16f1:8a80 1338395828 Q * brambles Remote host closed the connection 1338396957 Q * BenG Quit: I Leave 1338396985 Q * ensc|w Remote host closed the connection 1338396994 J * ensc|w ~ensc@www.sigma-chemnitz.de 1338397132 Q * ncopa Quit: Leaving 1338397311 J * brambles brambles@79.133.200.49 1338397448 J * hijacker ~hijacker@cable-84-43-134-121.mnet.bg 1338397619 Q * brambles Remote host closed the connection 1338397624 J * brambles brambles@79.133.200.49 1338397932 Q * brambles Remote host closed the connection 1338397941 J * brambles brambles@79.133.200.49 1338397992 J * fisted ~fisted@xdsl-78-35-84-129.netcologne.de 1338398249 Q * brambles Remote host closed the connection 1338398265 J * brambles brambles@79.133.200.49 1338398283 Q * fisted_ Ping timeout: 480 seconds 1338398573 Q * brambles Remote host closed the connection 1338398876 J * brambles brambles@79.133.200.49 1338399335 Q * Walex 1338399369 Q * brambles Ping timeout: 480 seconds 1338399449 J * brambles brambles@79.133.200.49 1338399757 Q * brambles Remote host closed the connection 1338399760 J * brambles brambles@79.133.200.49 1338400069 Q * brambles Remote host closed the connection 1338400072 J * brambles brambles@79.133.200.49 1338400127 Q * clopez Ping timeout: 480 seconds 1338400380 Q * brambles Remote host closed the connection 1338400382 J * brambles brambles@79.133.200.49 1338400689 Q * brambles Remote host closed the connection 1338400692 J * brambles brambles@79.133.200.49 1338401001 Q * brambles Remote host closed the connection 1338401006 J * brambles brambles@79.133.200.49 1338401314 Q * brambles Remote host closed the connection 1338401345 J * brambles brambles@79.133.200.49 1338401654 Q * brambles Remote host closed the connection 1338401657 J * brambles brambles@79.133.200.49 1338401965 Q * brambles Remote host closed the connection 1338401971 J * brambles brambles@79.133.200.49 1338402280 Q * brambles Remote host closed the connection 1338402282 J * brambles brambles@79.133.200.49 1338402590 Q * brambles Remote host closed the connection 1338402596 J * brambles brambles@79.133.200.49 1338402907 Q * brambles Remote host closed the connection 1338402938 J * brambles brambles@79.133.200.49 1338403247 Q * brambles Remote host closed the connection 1338403248 J * brambles brambles@79.133.200.49 1338403556 Q * brambles Remote host closed the connection 1338403558 J * brambles brambles@79.133.200.49 1338404535 J * petzsch ~markus@dslb-094-222-100-245.pools.arcor-ip.net 1338406773 J * fzylogic ~fzylogic@69.170.166.146 1338408658 J * benl ~benl@dockoffice.sonassihosting.com 1338408669 M * benl Hi all 1338409990 M * Bertl_oO hey 1338409994 N * Bertl_oO Bertl 1338410324 M * benl Can I bug you via pm? 1338410903 Q * hijacker Quit: Leaving 1338411899 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f 1338412177 Q * bonbons Quit: Leaving 1338413393 Q * arthus Quit: Lost terminal 1338413809 J * clopez ~clopez@200.19.165.83.dynamic.mundo-r.com 1338413815 Q * petzsch Read error: Connection reset by peer 1338413937 Q * ghislain Quit: Leaving. 1338415594 J * ghislain ~AQUEOS@adsl2.aqueos.com 1338415783 Q * ghislain 1338416312 J * BenG ~bengreen@cpc10-aztw24-2-0-cust114.aztw.cable.virginmedia.com 1338416911 M * benl I asked if there was a hard limit on file descriptors with guests 1338416919 M * benl and dhoziac said there was not 1338416935 M * benl but I'm seeing behaviour on multiple servers that imply there is 1338416971 M * benl as with shmmax and shmall - they have to be specifically set in /etc/vservers/x/sysctl/x/x - otherwise are at a prohibitively low level 1338416999 M * benl from stats I see a max of 1113 fd on a guest 1338417020 M * benl is there an explicit command to unlock these arbritrary limits on guests on resources? 1338417056 M * Bertl there are no limits by default except for the system defaults 1338417066 M * benl but there certainly is 1338417075 M * benl shmmall and shmmax are two prime examples 1338417092 M * benl even if they are set on the host (via sysctl.conf) - they are ignored in the guest 1338417111 M * Bertl the host is independant from the guest 1338417116 M * benl okay 1338417121 M * Bertl i.e. settings on the host do not affect the guests 1338417125 M * benl understood 1338417140 M * benl so, the guests inherit a "default" set of limits then? 1338417148 M * Bertl you get the default limits inside a guest, i.e. those you have on the host as well 1338417164 M * Bertl yes, but you can override them on a per guest basis 1338417176 M * Bertl (or via defaults as well) 1338417186 M * benl understoof 1338417189 M * benl *understood 1338417197 M * Bertl also note that there are limits per guest, and limits per user (inside each guest) 1338417218 M * benl I'm ignoring limits.conf for now .. 1338417228 M * Bertl the former are Linux-VServer specific, where the latter are a typical linux thing 1338417239 M * benl I understand 1338417277 M * benl is there documentation to define each "settable" systl setting? 1338417307 M * Bertl those are whatever the current linux kernel supports 1338417310 M * benl or is it the same syntax 1338417312 M * benl okay, great 1338417322 M * Bertl the Linux-VServer specific settings can be seen in cat /proc/virtual//limit 1338417344 M * Bertl you have a column labeled soft/hard there which shows the actual limits 1338417349 M * Bertl -1 means unlimited 1338417414 M * benl then I think there is a bug 1338417419 M * benl I've set a kernel.shmmax - and it works fine 1338417430 M * benl but /proc/virtual/x/limit shows -1 still ... 1338417467 M * Bertl yes, guest limit vs. sysctl limit 1338417490 M * benl no, I mean, the guest has kernel.shmmax set explicitally 1338417491 M * Bertl you can set the guest limits via vlimit 1338417495 M * benl in /etc/vservers/x/sysctl 1338417513 M * Bertl there are two different mechanisms at work 1338417516 M * benl and I can confirm it works (as the application in the guest trying to access the shared memory is no longer throwing errors) 1338417533 M * Bertl one which is provided from the namespace/cgroup environment 1338417545 M * Bertl and one which is imposed from the Linux-VServer patches 1338417604 M * Bertl note that in recent kernels the memory account is completely gone from the Linux-VServer limits 1338417605 M * benl right ... 1338417619 M * Bertl (i.e. replaced by cgroups) 1338417623 M * benl I'm referring to 2.6.32 1338417786 Q * BenG Quit: I Leave 1338417800 M * benl is there a way to increase file descriptors for a guest on-the-fly 1338417904 M * Bertl depends on which limit you are talking about 1338417920 M * Bertl the Linux-VServer limit can be adjusted with vlimit 1338417936 M * Bertl (but that is most likely not set at all) 1338417970 M * Bertl the ulimits (hard and soft) can be changed from inside the guest spaces given you have the required priviledges 1338418026 M * Bertl (but they only apply to newly started processes, that's how Linux is designed) 1338418062 M * benl I get that 1338418078 M * benl so if I wanted to set kern.shmall in the guest ... 1338418117 M * Bertl you best enter the guest namespace (in this case ipc at least) and set it with the appropriate sysctl 1338418238 M * benl I assume you mean the management namespace 1338418244 M * benl ie. not vserver guest enter 1338418659 M * Bertl not 'enter' unless your guest root is allowed to do such changes 1338418676 M * Bertl (by default it isn't) 1338419338 M * benl ahah 1338419342 M * benl makes more sense 1338419358 M * benl would the right command be vnamespace -e x bash 1338419404 M * Bertl with two dashes before the bash and x being the xid, yes 1338419422 M * benl actually, i meant, vnamespace -e myguetsname bash 1338419460 M * benl so from there, I should be able to use sysctl? as that seems to display the host config 1338419509 M * Bertl try to enter the --ipc namespace and use the dashes 1338419611 M * benl vnamespace -e XID --ipc -- bash ... ? 1338419667 M * Bertl yup, that will enter the ipc namespace, given that your kernel supports it 1338419703 M * benl well, it entered something 1338419724 M * benl but again, sysctl -p and cat /proc/kern.....shmmax shows the host value - not the guest's 1338419849 M * benl right, i think i see whats going on 1338419882 M * benl the namespace is the guest, but running sysctl -p, is now setting the host values, on the guest 1338419922 M * benl yeah, okay, that makes sense now 1338419972 M * benl vserver guest exec cat /proc/sys/kernel/shmmax now shows the new value