1260057614 M * badiane ok cool, that simple huh! :-) 1260057665 M * Bertl note that the guest configs fstab uses host relative pathes for the 'from/device' part and guest relative ones for the mountpoint 1260058099 Q * snooky 1260058121 J * friendly ~friendly@ppp118-209-31-140.lns20.mel4.internode.on.net 1260058490 M * badiane ok 1260058492 M * badiane got it 1260058687 M * badiane quick question, is there a place where I can drop a debootstrap package so that it doesn't have to be hunted for? 1260058981 M * Bertl install it on the host 1260059432 M * badiane and how will the vserver build command know of it's existence 1260059559 M * badiane I am receiving a Internal Error! from vserver-copy. I'm trying to copy a template vserver that I created to a new one. The new directory which will serve as target for the new copy is already created (it's a mount point for a LVM slice). 1260059599 M * badiane could that cause the Internal Error! message? 1260059851 M * Bertl what's vserver-copy? 1260059989 M * badiane util-vserver-0.30.216: /usr/local/sbin/vserver-copy 1260060034 J * blues_ ~blues@bqo45.neoplus.adsl.tpnet.pl 1260060035 M * Bertl the legacy script should not be used, it's deprecated 1260060085 M * badiane ok 1260060102 M * badiane what should I use if I want to cp a template to a new server? 1260060116 M * Bertl vserver - build --help 1260060120 M * badiane ok 1260060134 M * Bertl you can use 'clone' locally, or rsync local & remote 1260060151 M * Bertl or if you have a tar/archive use the template methode 1260060154 Q * blues Ping timeout: 480 seconds 1260060177 M * badiane it's a local vserver to a new one 1260060265 M * Bertl so probably 'clone' is your best choice 1260060279 M * Bertl if the guest is unified, it will be quite quick 1260060296 Q * geb Quit: / 1260060506 M * badiane not unified 1260060511 M * badiane it's my first 1260060515 M * Bertl np 1260060519 M * badiane brb 1260060894 Q * dna Quit: Verlassend 1260061915 M * badiane back 1260061921 M * Bertl wb 1260061929 M * badiane thanks 1260061962 M * badiane I noticed that the version of util-vserver that I'm using placed the vserver-build command in /usr/local/lib/util-vserver/ 1260061980 M * badiane is that where it's supposed to be? 1260062002 M * Bertl well, no, it's the default if you do not configure util-vserver at build time 1260062069 M * badiane so where should the executables reside? 1260062074 M * badiane normally 1260062099 M * Bertl I usually configure them to be in /usr, with /vservers as guest path 1260062131 M * Bertl debian does put the guests in /var/lib/vservers, but most distros agree on /etc/vservers for the config 1260062143 M * badiane I configured the guest path to be located under srv as per man hier 1260062168 M * badiane configs are in /usr/local/etc 1260062197 M * Bertl as daniel uses to say: whatever rows your boat :) 1260062201 M * badiane I'm fine with /usr/local 1260062203 M * badiane :-) 1260062223 M * badiane and there are vserver executables in /usr/local/sbin 1260062298 M * badiane namely the vserver-copy, but vserver-build was left in /usr/local/lib/util-vserver/. I'm going to link them to /usr/local/sbin so that I may have access to them 1260062316 M * badiane I hope that doesn't transgress some golden rule 1260062413 M * Bertl well, both are deprecated and counted as old legacy 1260062439 M * Bertl i.e. do not expect them to work unless you are on linux-2.4 1260062546 M * badiane so what would be considered up to date? 1260062580 M * Bertl vserver - build --help 1260062633 M * badiane that's one hyphenated word correct (just making sure)? 1260062657 M * Bertl the dash is a placeholder 1260062670 M * Bertl i.e. you can use 'vserver none build --help' as well 1260062695 M * badiane ok 1260062720 M * badiane nice 1260062840 Q * imcsk8 Quit: This computer has gone to sleep 1260062993 M * badiane this is so cool 1260062995 M * badiane ;-) 1260063006 M * Bertl :) 1260063123 J * imcsk8 ~ichavero@evdomip-79-4.iusacell.net 1260063376 Q * imcsk8 1260064467 J * imcsk8 ~ichavero@evdomip-79-4.iusacell.net 1260064660 Q * imcsk8 1260064910 M * Bertl off to bed now .. have a good one everyone! 1260064914 N * Bertl Bertl_zZ 1260067386 J * eja_ ~eric@75.111.56.37 1260067387 Q * eja Read error: Connection reset by peer 1260068447 J * derjohn_foo ~aj@e180193242.adsl.alicedsl.de 1260068770 Q * FireEgl Quit: Leaving... 1260068804 Q * aj__ Read error: Connection reset by peer 1260071604 Q * Yepsen Ping timeout: 480 seconds 1260071639 J * Yepsen ~yepsen@pdbn-5d827975.pool.mediaWays.net 1260072040 J * saulus_ ~saulus@d003184.adsl.hansenet.de 1260072406 Q * SauLus Ping timeout: 480 seconds 1260072417 N * saulus_ SauLus 1260073139 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com 1260074097 Q * FireEgl Remote host closed the connection 1260076799 J * FireEgl Proteus@2001:470:e056:1:fce5:b123:8e68:d6fc 1260079124 J * geb ~geb@234.4.82-79.rev.gaoland.net 1260079716 Q * geb Ping timeout: 480 seconds 1260081156 J * balbir ~balbir@122.172.20.233 1260083065 Q * cuba33ci Read error: Connection reset by peer 1260083119 J * cuba33ci ~cuba33ci@118-168-237-103.dynamic.hinet.net 1260085214 Q * SauLus reticulum.oftc.net joule.oftc.net 1260085214 Q * derjohn_foo reticulum.oftc.net joule.oftc.net 1260085214 Q * larsivi reticulum.oftc.net joule.oftc.net 1260085214 Q * mcp reticulum.oftc.net joule.oftc.net 1260085214 Q * gerrit reticulum.oftc.net joule.oftc.net 1260085214 Q * urbee reticulum.oftc.net joule.oftc.net 1260085214 Q * biz reticulum.oftc.net joule.oftc.net 1260085214 Q * transacid reticulum.oftc.net joule.oftc.net 1260085214 Q * manana reticulum.oftc.net joule.oftc.net 1260085214 Q * Swen_awaY reticulum.oftc.net joule.oftc.net 1260085214 Q * wibble reticulum.oftc.net joule.oftc.net 1260085214 Q * Mr_Smoke reticulum.oftc.net joule.oftc.net 1260085214 Q * m_o_d reticulum.oftc.net joule.oftc.net 1260085214 Q * Wonka reticulum.oftc.net joule.oftc.net 1260085214 Q * eyck_ reticulum.oftc.net joule.oftc.net 1260085214 Q * zbyniu reticulum.oftc.net joule.oftc.net 1260085214 Q * sladen reticulum.oftc.net joule.oftc.net 1260085214 Q * AndrewLee reticulum.oftc.net joule.oftc.net 1260085214 Q * Marillion reticulum.oftc.net joule.oftc.net 1260085214 Q * PowerKe reticulum.oftc.net joule.oftc.net 1260085214 Q * Chlorek reticulum.oftc.net joule.oftc.net 1260085214 Q * FloodServ reticulum.oftc.net joule.oftc.net 1260085214 Q * MooingLemur reticulum.oftc.net joule.oftc.net 1260085214 Q * balbir reticulum.oftc.net joule.oftc.net 1260085214 Q * bkk reticulum.oftc.net joule.oftc.net 1260085214 Q * fback reticulum.oftc.net joule.oftc.net 1260085214 Q * padde reticulum.oftc.net joule.oftc.net 1260085214 Q * kjj reticulum.oftc.net joule.oftc.net 1260085214 Q * gdm reticulum.oftc.net joule.oftc.net 1260085214 Q * smash reticulum.oftc.net joule.oftc.net 1260085214 Q * nkukard reticulum.oftc.net joule.oftc.net 1260085214 Q * DreamerC reticulum.oftc.net joule.oftc.net 1260085214 Q * blathijs reticulum.oftc.net joule.oftc.net 1260085214 Q * friendly reticulum.oftc.net joule.oftc.net 1260085214 Q * evilhackerdude reticulum.oftc.net joule.oftc.net 1260085214 Q * tam reticulum.oftc.net joule.oftc.net 1260085214 Q * quasisane reticulum.oftc.net joule.oftc.net 1260085214 Q * faheem reticulum.oftc.net joule.oftc.net 1260085214 Q * karasz reticulum.oftc.net joule.oftc.net 1260085214 Q * puck reticulum.oftc.net joule.oftc.net 1260085214 Q * micah reticulum.oftc.net joule.oftc.net 1260085214 Q * eja_ reticulum.oftc.net joule.oftc.net 1260085214 Q * sardyno reticulum.oftc.net joule.oftc.net 1260085214 Q * carnage reticulum.oftc.net joule.oftc.net 1260085214 Q * badiane reticulum.oftc.net joule.oftc.net 1260085214 Q * fzylogic reticulum.oftc.net joule.oftc.net 1260085214 Q * Snow-Man reticulum.oftc.net joule.oftc.net 1260085214 Q * agaffney reticulum.oftc.net joule.oftc.net 1260085214 Q * cuba33ci reticulum.oftc.net joule.oftc.net 1260085214 Q * nox reticulum.oftc.net joule.oftc.net 1260085214 Q * mEDI_S reticulum.oftc.net joule.oftc.net 1260085223 Q * nenolod reticulum.oftc.net joule.oftc.net 1260085223 Q * isodude reticulum.oftc.net joule.oftc.net 1260085223 Q * arachnist reticulum.oftc.net joule.oftc.net 1260085223 Q * bzed reticulum.oftc.net joule.oftc.net 1260085223 Q * FireEgl reticulum.oftc.net joule.oftc.net 1260085223 Q * blues_ reticulum.oftc.net joule.oftc.net 1260085223 Q * Hollow reticulum.oftc.net joule.oftc.net 1260085223 Q * theocrite reticulum.oftc.net joule.oftc.net 1260085223 Q * hijacker reticulum.oftc.net joule.oftc.net 1260085223 Q * Guy- reticulum.oftc.net joule.oftc.net 1260085223 Q * ex reticulum.oftc.net joule.oftc.net 1260085223 Q * FIChTe reticulum.oftc.net joule.oftc.net 1260085223 Q * matthew-_ reticulum.oftc.net joule.oftc.net 1260085223 Q * pmjdebruijn reticulum.oftc.net joule.oftc.net 1260085223 Q * jpic_ reticulum.oftc.net joule.oftc.net 1260085223 Q * opuk reticulum.oftc.net joule.oftc.net 1260085223 Q * Loki|muh reticulum.oftc.net joule.oftc.net 1260085223 Q * fosco reticulum.oftc.net joule.oftc.net 1260085223 Q * _Shiva_ reticulum.oftc.net joule.oftc.net 1260085223 Q * Psy0rz reticulum.oftc.net joule.oftc.net 1260085223 Q * harry reticulum.oftc.net joule.oftc.net 1260085223 Q * grobie reticulum.oftc.net joule.oftc.net 1260085223 Q * mkee reticulum.oftc.net joule.oftc.net 1260085223 Q * daniel_hozac reticulum.oftc.net joule.oftc.net 1260085223 Q * Radiance reticulum.oftc.net joule.oftc.net 1260085223 Q * mnemoc reticulum.oftc.net joule.oftc.net 1260085223 Q * elesouef reticulum.oftc.net joule.oftc.net 1260085223 Q * Hunger reticulum.oftc.net joule.oftc.net 1260085223 Q * Yepsen reticulum.oftc.net joule.oftc.net 1260085223 Q * nou reticulum.oftc.net joule.oftc.net 1260085223 Q * cehteh reticulum.oftc.net joule.oftc.net 1260085223 Q * Piet reticulum.oftc.net joule.oftc.net 1260085223 Q * jrklein reticulum.oftc.net joule.oftc.net 1260085223 Q * thermoman reticulum.oftc.net joule.oftc.net 1260085223 Q * DelTree reticulum.oftc.net joule.oftc.net 1260085223 Q * raceme reticulum.oftc.net joule.oftc.net 1260085223 Q * snooze reticulum.oftc.net joule.oftc.net 1260085287 Q * ard reticulum.oftc.net joule.oftc.net 1260085287 Q * DLange reticulum.oftc.net joule.oftc.net 1260085287 Q * thalunil reticulum.oftc.net joule.oftc.net 1260085287 Q * yang reticulum.oftc.net joule.oftc.net 1260085287 Q * neofutur reticulum.oftc.net joule.oftc.net 1260085287 Q * Sirenia reticulum.oftc.net joule.oftc.net 1260085287 Q * trippeh reticulum.oftc.net joule.oftc.net 1260085287 Q * C14r reticulum.oftc.net joule.oftc.net 1260085287 Q * tokkee reticulum.oftc.net joule.oftc.net 1260085287 Q * SpComb reticulum.oftc.net joule.oftc.net 1260085287 Q * kiorky Remote host closed the connection 1260085310 Q * weasel Nick collision 1260085314 Q * ascii Ping timeout: 480 seconds 1260086107 T * * http://linux-vserver.org/ |stable 2.2.0.7, devel 2.3.0.34, grsec 2.3.0.36|util-vserver-0.30.215|libvserver-1.0.2|vserver-utils-1.0.3| He who asks a question is a fool for a minute; he who doesn't ask is a fool for a lifetime -- share the gained knowledge on the Wiki, and we forget about the minute. 1260086107 T * ChanServ - 1260086307 J * FireEgl Proteus@2001:470:e056:1:fce5:b123:8e68:d6fc 1260087142 Q * FireEgl Ping timeout: 480 seconds 1260087704 J * FireEgl Proteus@2001:470:e056:1:fce5:b123:8e68:d6fc 1260088047 J * ghislain ~AQUEOS@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1260089055 Q * ghislain Quit: Leaving. 1260089118 J * ghislain ~AQUEOS@LPuteaux-151-41-11-129.w217-128.abo.wanadoo.fr 1260089683 Q * FireEgl Ping timeout: 480 seconds 1260091113 M * ghislain daniel_hozac: is it possible to add informations and exemples to the great flower page wiki style ? 1260091131 M * ghislain daniel_hozac: i mean the content not the css 1260093087 J * friendly ~friendly@ppp118-209-31-140.lns20.mel4.internode.on.net 1260093330 M * ghislain mount 1260093450 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1260094523 Q * arekm_ Quit: leaving 1260094573 J * arekm arekm@carme.pld-linux.org 1260094700 M * blathijs ghislain: IIRC the flower page sources are somewhere in the util-vserver source tree, so you can submit patches to that. 1260095695 Q * bzed Remote host closed the connection 1260095701 J * bzed ~bzed@devel.recluse.de 1260095770 P * friendly 1260096575 Q * bzed Ping timeout: 480 seconds 1260096841 J * bzed_ ~bzed@devel.recluse.de 1260097151 N * bzed_ bzed 1260100199 N * Bertl_zZ_ Bertl 1260100205 M * Bertl morning folks! 1260100239 M * pmjdebruijn morning 1260102295 M * ghislain bertl: morning 1260104439 M * Bertl off for now ... bbl 1260104443 N * Bertl Bertl_oO 1260107189 Q * bkk Quit: Leaving. 1260107304 J * lvps ~blagoj@89.205.102.23 1260110252 Q * eja_ Read error: Connection reset by peer 1260110270 J * eja ~eric@75.111.56.37 1260113287 N * Bertl_oO Bertl 1260113290 M * Bertl back now ... 1260114469 J * imcsk8 ~ichavero@evdomip-79-4.iusacell.net 1260115061 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com 1260115233 J * Loki_muh loki@satanix.de 1260115233 Q * Loki|muh Read error: Connection reset by peer 1260115244 N * Loki_muh Loki|muh 1260115404 J * kjj_ ~kjj@pool-74-107-128-126.ptldor.fios.verizon.net 1260115752 Q * kjj Ping timeout: 480 seconds 1260115752 N * kjj_ kjj 1260116188 Q * imcsk8 Quit: This computer has gone to sleep 1260116528 M * jrklein Good morning everyone! I migrated some 32-bit guests to some 64-bit hosts about a week ago. I just realized that a "uname -a" within the guest shows that the formerly 32-bit guest now has a 64-bit kernel. Should I go ahead and set 32-bit personality to hide the host's 64-bit kernel from the guest (ie: show a 32-bit kernel within guest), or does it matter? Not sure what the benefit of this would be. I just assumed running a 32-bit gues 1260116528 M * jrklein without setting 32-bit personality didn't work at all, so I was surprised when I stumbled across this today. 1260116647 M * jrklein PS - As per the "32 vs 64 Bit" item in the FAQ, I had already enabled the necessary 32-bit emulation options when I built the kernel. I just forgot to configure the /personality and /uts/machine files for a 32-bit environment in each of these migrated guests. 1260116758 J * imcsk8 ~ichavero@evdomip-79-4.iusacell.net 1260117678 Q * Loki|muh Ping timeout: 480 seconds 1260117967 Q * imcsk8 Quit: This computer has gone to sleep 1260118300 M * badiane hello everyone 1260118478 M * Bertl jrklein: you need to set the personality, but uts machine changes are not really required 1260118653 M * jrklein bertl: thanks. so I should set the personality back to 32-bit on those guests that were originally 32-bit guests? 1260118737 J * Loki|muh loki@satanix.de 1260118847 M * Bertl back to? what did you set them to now? 1260119147 M * jrklein personality on the formerly 32-bit guests is not set at all right now, so it's inheriting the 64-bit personality from the host. 1260119215 M * Bertl correct, so it should be _set_ to 32bit, not set _back_ to 32bit :) 1260119997 M * badiane I noticed that a vserver can be renamed with the --force option, do I have to pass a method? What would be the good way of doing this? 1260120085 M * jrklein will set them to 32bit personality. sorry about not being clear about that. :) just out of curiosity, does this save memory or prevent other complications down the road? surprised that not setting 32bit personality for these guests worked at all. 1260120421 J * geb ~geb@earth.gebura.eu.org 1260123391 Q * niki_ Ping timeout: 480 seconds 1260124209 J * niki_ ~niki@0x5553169c.adsl.cybercity.dk 1260124762 M * faheem hi. vservers on my machine (Debian lenny) currently inaccessible via ssh. can anyone help? 1260124946 M * Bertl host or guest 1260125020 M * Bertl I presume the guests :) 1260125085 M * Bertl faheem: http://linux-vserver.org/Frequently_Asked_Questions#When_I_try_to_ssh_to_the_guest.2C_I_log_into_the_host.2C_even_if_I_installed_sshd_on_the_guest._What.27s_wrong_here.3F 1260125560 M * faheem Bertl: i think the guests 1260125589 M * faheem the host is not a vserver, is it? 1260125614 M * faheem also, when starting a vserver right now, I got: Enabling additional executable binary formats: binfmt-supportFATAL: Could not load /lib/modules/2.6.26-2-vserver-686-bigmem/modules.dep: No such file or directory 1260125618 M * faheem update-binfmts: warning: Couldn't load the binfmt_misc module. 1260125627 M * faheem is this something to be concerned about? 1260125764 M * faheem yes, my sshd config is already correct 1260125893 M * faheem i'm only seeing this problem with some vservers. one which i upgraded from etch 1260125896 M * faheem to lenny 1260126320 M * faheem i have one which i think was originally lenny (not upgrade from etch) which seems fine. 1260126624 M * Bertl no, it just shows that your guest is not cleaned up properly (i.e. it should not try to do that, but it is harmless) 1260126677 M * faheem Bertl: ok 1260126709 M * faheem what debugging approach to you suggest for the vservers not reachable via ssh? 1260126789 M * Bertl well, you still need to tell me the details 1260126805 M * Bertl host is reachable yes/no? any guest reachable yes/no? 1260126851 M * faheem Bertl: host is the main desktop machine? i'm sitting at the console. 1260126861 M * faheem some guests reachable, others not 1260126893 M * faheem guests reachable appear to correspond to not upgraded from etch. 1260126907 M * faheem guests not reachable appear to correspond to those upgrade from etch 1260126944 M * Bertl well, then chances are good that the guests themselves have some userspace issue 1260126955 M * Bertl check inside one of those guests that sshd is running 1260126970 M * Bertl also check the logs (inside the guest) for issues 1260127003 M * faheem Bertl: it is running. ok, checking logs now 1260127033 M * Bertl you might want to start sshd manually with debug enabled (for sshd) and see what happens on a logon 1260127041 M * faheem Bertl: i see - ssh: connect to host 192.168.1.204 port 22: No route to host 1260127042 M * Bertl could be pam limits or session management 1260127068 M * faheem which log? 1260127082 M * Bertl hmm? 1260127100 M * faheem Bertl: I'm seeing - Jun 26 06:39:01 msi pam_limits[30357]: setrlimit limit #11 to soft=-1, hard=-1 failed: Operation not permitted; uid=0 euid=0 1260127110 M * faheem in auth.log on the guest. what does this mean? 1260127124 M * faheem Bertl: i meant, what log(s) should I look at? 1260127133 M * Bertl that means, that your pam config tries to unset the limit #11 1260127153 M * Bertl and is very likely your issue 1260127157 M * faheem Bertl: ok 1260127219 M * faheem can you elaborate on why this is happening, and how to fix it? 1260127248 M * faheem i have no idea what this limit signifies 1260127268 M * Bertl what arch are you on? 1260127274 M * faheem Bertl: i386 1260127281 M * faheem both host and guests 1260127291 M * faheem i guess that is redundant 1260127348 M * faheem i don't see any message corresponding to my recent attempts to log in, though 1260127379 M * Bertl #define RLIMIT_SIGPENDING 11 /* max number of pending signals */ 1260127422 M * faheem Bertl: pardon? 1260127442 M * Bertl that's limit #11 1260127467 M * Bertl what's in your /etc/limits.conf ? 1260127469 M * Bertl (please use paste.linux-vserver.org for everything longer than 3 lines) 1260127509 M * faheem Bertl: ok 1260127519 M * faheem Bertl: don't seem to have a /etc/limits.conf 1260127636 M * Bertl /etc/security/limits.conf maybe? 1260127642 M * faheem Bertl: yes. hang on 1260127671 M * faheem the whole thing is just one big comment 1260127680 M * faheem comparing to lenny's version. sec 1260127783 M * faheem looks identical to the version on host 1260127832 M * Bertl obviously _something_ is calling setrlimit with higher limits than the guest config allow 1260127884 M * Bertl you can configure the guest to ignore those raises or lift the limit for the guest completely (not advised) or find the cause, i.e. the script/tool calling that 1260127887 M * faheem Bertl: hmm 1260127902 M * faheem not a known problem then? 1260127937 M * Bertl not to me, but I don't have debian guests atm 1260127956 M * Bertl (and I'm using recent kernels/tools :) 1260127960 M * faheem Bertl: not reported here, though? people would tend to come here with problems 1260128026 M * Bertl last time it was fixed in limits.conf IIRC 1260128040 M * Bertl and it was caused by pam/limits 1260128115 M * faheem Bertl: i don't see a pam/limits 1260128239 M * Bertl grep limit /etc/pam.d/* 1260128341 M * faheem Bertl: nothing under there. 1260128358 M * faheem hits are mostly comments 1260128416 M * faheem could try asking on #debian, i suppose 1260129232 M * faheem Bertl: let me make sure i understand the issue clearly. there is something called an rlimit 1260129251 M * faheem the guest config has a limit on it (what is that limit and where is it set)? 1260129287 M * faheem and something else is trying to raise it (from limit #11 to soft=-1, hard=-1)? 1260129309 M * faheem can i query the system to ask what the rlimit is currently set to? 1260129851 M * daniel_hozac use ulimit 1260129884 M * faheem daniel_hozac: ulimit says unlimited 1260131795 M * Bertl faheem: the problem is, the host has some limits set (hard/soft) which are inhereted by the guest (if not overwritten in the config) 1260131806 M * Bertl by default, the guest is not allowed 1260131824 M * Bertl to raise those limits (hard) 1260131878 M * faheem Bertl: ok 1260131897 M * faheem so, what is going wrong here, exactly? 1260131940 M * faheem is it that the guest should not be trying to raise the limits at all? 1260132201 M * Bertl basically yes, but as I said, there is a workaround 1260132264 J * cuba33ci_ ~cuba33ci@118-160-165-184.dynamic.hinet.net 1260132302 M * Bertl the simplest is to change the guest limits to be as high as the guest sets them 1260132315 M * Bertl given that this is acceptable security wise 1260132339 M * Bertl of course, the better approach is to set the guest limits as low as the host limits (or the guest config) 1260132372 Q * cuba33ci Ping timeout: 480 seconds 1260132522 Q * ghislain Quit: Leaving. 1260132574 M * faheem Bertl: changing the guest limits sounds ok. 1260132583 M * faheem how would i do that? 1260132606 M * faheem is this part of the vserver config? 1260132750 M * faheem Bertl: security is not really a concern here. this is for my own personal use, and the vservers are not publicly accessible 1260132811 M * Bertl then just put unlimited into the guest configs ulimits 1260132820 M * Bertl (for this limit) 1260133663 J * imcsk8 ~ichavero@evdomip-79-4.iusacell.net 1260133673 N * DoberMann[PullA] DoberMann[ZZZzzz] 1260135507 M * faheem Bertl: where does the guest configs ulimit live? 1260135537 M * faheem you mean the /etc/security/limits.conf? 1260135620 M * daniel_hozac /etc/vservers//ulimits 1260136541 Q * bonbons Quit: Leaving 1260137192 J * dna ~dna@p54BCAA59.dip0.t-ipconnect.de 1260137263 M * faheem daniel_hozac: thanks 1260137415 M * faheem daniel_hozac: there is currently no such file. should i create one? if so, what should i put in it? 1260137423 M * Bertl daniel_hozac: hmm, 2.6.32 seems quite broken ... so chances are really good that it will become the next debian stable kernel :) 1260137424 M * faheem rlimit = unlimited 1260137428 M * faheem ? 1260137460 Q * derjohn_foo Remote host closed the connection 1260137694 M * Bertl faheem: http://www.nongnu.org/util-vserver/doc/conf/configuration.html 1260137743 M * Bertl but I do not see the signals listed in the docu, so maybe daniel_hozac can clarify 1260137773 J * derjohn_mob ~aj@e180193242.adsl.alicedsl.de 1260138323 M * faheem Bertl: ok. thanks. 1260138337 M * faheem daniel_hozac: what are your thoughts? 1260138970 Q * dna Quit: Verlassend 1260141303 Q * imcsk8 Quit: This computer has gone to sleep