1197417757 Q * dowdle Remote host closed the connection
1197418043 Q * rob-84x^ Ping timeout: 480 seconds
1197418073 Q * meebey Remote host closed the connection
1197418103 J * meebey meebey@booster.qnetp.net
1197420314 J * FireEgl FireEgl@Sebastian.Atlantica.US
1197421003 J * edesche1 ~edeschen@proxy-sjc-2.cisco.com
1197421271 J * edeschen ~edeschen@proxy-sjc-2.cisco.com
1197421305 Q * edeschen Quit: Leaving
1197422596 Q * Abaddon Quit: leaving
1197422909 M * edesche1 Hi, I have a question about "init-style=plain" and "vserver stop". When using "plain" as init-style, the" vserver stop" command always force kill the vserver after a timeout occurs. I found on the IRC logs (March 2006) an interesting thread about this (http://irc.13thfloor.at/LOG/2006-03/LOG_2006-03-24.txt) I was wondering if any solution or workaround to gracefully to kill the init process running in the VServer when vserver stop is invoked.
1197425004 Q * meebey Remote host closed the connection
1197425035 J * meebey meebey@booster.qnetp.net
1197426211 M * daniel_hozac what distribution for the guest, and what utils?
1197426221 M * daniel_hozac because it's supposed to work fine...
1197426269 M * daniel_hozac (also assuming a recent enough kernel)
1197426299 Q * mire Read error: Operation timed out
1197426447 M * edesche1 daniel_hozac: we use redhat based environment. Kernel+VServer: 2.6.22.9-vs2.2.0.4
1197426505 M * edesche1 cat /etc/redhat-release
1197426510 M * edesche1 Fedora Core release 6 (Zod)
1197426566 M * daniel_hozac okay, inside the guest, what does /etc/init.d/halt look like?
1197426626 J * mastaj ~skateblin@216-15-77-93.c3-0.tlg-ubr2.atw-tlg.pa.cable.rcn.com
1197426633 M * mastaj helo
1197426648 M * mastaj anyone have  linux and can help me out?
1197426668 P * mastaj 
1197426728 M * edesche1 daniel: I copied the /sbin/halt from the host to the vserver as is
1197426735 M * edesche1 from FC6
1197426746 M * edesche1 still times out
1197426750 M * daniel_hozac not /sbin/halt, /etc/init.d/halt.
1197426803 M * edesche1 yeah, copied /etc/init.d/halt from host to the guest. also copied the /sbin/bin/halt
1197426822 M * daniel_hozac and?
1197426831 M * edesche1 still does not work
1197426837 M * edesche1 times out
1197426846 M * daniel_hozac and you have util-vserver 0.30.214 or thereabouts, yes?
1197426947 M * edesche1 [root@appre-pc1 init.d]# vserver --version
1197426947 M * edesche1 vserver 0.30.214 -- manages the state of vservers
1197426947 M * edesche1 This program is part of util-vserver 0.30.214
1197426985 M * edesche1 I may be missing something very basic here
1197426995 M * daniel_hozac how did you build the guest?
1197427079 N * ensc Guest966
1197427089 J * ensc ~irc-ensc@77.235.182.26
1197427090 M * edesche1 I used the /sbin/vserver build -m skeleton
1197427114 M * edesche1 and copied miminum files from the host to get a FC6ish environment
1197427145 M * daniel_hozac just FYI, FC6 is EOL.
1197427164 M * daniel_hozac but anyway, is there a reason you didn't use vserver ... build -m yum?
1197427185 M * edesche1 yeah, embedded system, just want the minimum to run
1197427188 Q * Guest966 Ping timeout: 480 seconds
1197427203 M * edesche1 I guess I can build another vserver instance using yum and try it out
1197427232 M * daniel_hozac -m yum just pulls in the packages needed to run the initscripts.
1197427233 M * edesche1 I just thought I was missing something basic and wanted to know what the outcome of the discussion I had seen had been fixed
1197427242 M * daniel_hozac yes, it's all fixed.
1197427263 M * edesche1 ok thanks Daniel, I'll try the yum approach
1197427277 M * daniel_hozac as long as the guest calls sys_reboot(HALT) as part of the shutdown procedure, everything should be fine.
1197430276 J * friendly12345 ~friendly@ppp121-44-206-97.lns3.mel4.internode.on.net
1197431657 J * _gh_ ~gerrit@1406chost40.starwoodbroadband.com
1197433228 Q * meebey Remote host closed the connection
1197433258 J * meebey meebey@booster.qnetp.net
1197434098 J * undefined ~undefined@adsl-68-94-183-129.dsl.rcsntx.swbell.net
1197434195 Q * shuri Quit: This computer has gone to sleep
1197434527 Q * undefined Excess Flood
1197434864 J * undefined ~undefined@adsl-68-94-183-129.dsl.rcsntx.swbell.net
1197435201 Q * zLinux_ Remote host closed the connection
1197435265 Q * daniel_hozac Ping timeout: 480 seconds
1197435441 J * daniel_hozac ~daniel@ssh.hozac.com
1197436122 J * balbir ~balbir@122.167.208.28
1197436803 Q * fatgoose_ Quit: fatgoose_
1197437081 P * undefined 
1197439053 J * shuri ~shuri@64.235.209.226
1197439131 N * _jthm_ infowolfe
1197439136 M * infowolfe moin Bertl 
1197439202 Q * edesche1 Remote host closed the connection
1197439428 J * sharkjaw ~gab@shell.ormset.no
1197440761 J * ntrs ~ntrs@79.125.235.118
1197442495 Q * balbir Ping timeout: 480 seconds
1197443202 J * balbir ~balbir@122.167.179.91
1197443346 J * dreamind ~dreamind@C2107.campino.wh.tu-darmstadt.de
1197443377 M * dreamind Morning :)
1197444576 Q * meebey Remote host closed the connection
1197444606 J * meebey meebey@booster.qnetp.net
1197444806 Q * Aiken_ Quit: Leaving
1197445625 J * JonB ~NoSuchUse@kg1-98.kollegiegaarden.dk
1197447160 Q * meebey Remote host closed the connection
1197447190 J * meebey meebey@booster.qnetp.net
1197447386 M * infowolfe Bertl, the warning about mtu on interfaces...
1197447392 M * infowolfe does it happen on e1000?
1197447709 J * gebura ~gebura@77.192.186.197
1197447727 M * gebura hi
1197447878 M * daniel_hozac hello
1197448119 Q * JonB Quit: This computer has gone to sleep
1197448815 N * ensc Guest995
1197448815 Q * Guest995 Read error: Connection reset by peer
1197448825 J * ensc ~irc-ensc@77.235.182.26
1197449315 J * mire ~mire@91-171-222-85.adsl.verat.net
1197449389 J * Aiken ~james@ppp121-45-246-228.lns2.bne4.internode.on.net
1197449509 Q * dreamind Quit: dreamind
1197452332 J * ard6 ~ard@gw-office.telegraaf.net
1197452530 Q * ard6 
1197452784 J * ard6 ~ard@2002:d9c4:2909:1::1
1197453396 J * dna ~dna@83-200-dsl.kielnet.net
1197453428 J * esa` ~esa@ip-87-238-2-45.adsl.cheapnet.it
1197453438 Q * esa Ping timeout: 480 seconds
1197453880 J * Abaddon abaddon@68-71.is.net.pl
1197454459 Q * dna Read error: Connection reset by peer
1197454523 J * dna ~dna@83-200-dsl.kielnet.net
1197454615 Q * Adrinael_ Ping timeout: 480 seconds
1197454630 Q * larsivi Quit: Konversation terminated!
1197454944 J * Adrinael adrinael@rid7.kyla.fi
1197455274 Q * Hunger Ping timeout: 480 seconds
1197455481 Q * hparker Quit: Read error: 104 (Peer reset by connection)
1197455636 Q * dna Read error: Connection reset by peer
1197455825 J * dna ~dna@83-200-dsl.kielnet.net
1197456144 J * Hunger Hunger.hu@Hunger.hu
1197456579 P * friendly12345 
1197457187 J * WDTY ~chatzilla@88.159.1.100
1197457225 Q * the-me Ping timeout: 480 seconds
1197457441 J * JonB ~NoSuchUse@kg1-98.kollegiegaarden.dk
1197457882 J * larsivi ~larsivi@85.221.53.194
1197458332 Q * Abaddon Quit: leaving
1197458521 J * virtuoso_ ~s0t0na@ppp91-122-160-12.pppoe.avangard-dsl.ru
1197458878 J * Julius ~julius@p57B25942.dip.t-dialin.net
1197458924 Q * virtuoso Ping timeout: 480 seconds
1197459373 J * the-me Patrick@Linux-Dev.org
1197459414 J * pmenier ~pme@LNeuilly-152-22-72-5.w193-251.abo.wanadoo.fr
1197459450 Q * Julius Ping timeout: 480 seconds
1197459649 J * matti matti@acrux.romke.net
1197459775 M * matti :)
1197459818 Q * tam Remote host closed the connection
1197459949 Q * JonB Ping timeout: 480 seconds
1197460122 J * Julius ~julius@p57B25942.dip.t-dialin.net
1197460182 J * tam ~tam@gw.nettam.com
1197460685 N * pmenier pmenier_off
1197460685 Q * meebey Remote host closed the connection
1197460716 J * meebey meebey@booster.qnetp.net
1197461551 Q * FloodServ charon.oftc.net services.oftc.net
1197462881 J * Pyxcad ~jircii@81-174-56-148.static.ngi.it
1197463303 J * FloodServ services@services.oftc.net
1197463341 Q * FloodServ charon.oftc.net services.oftc.net
1197463395 J * FloodServ services@services.oftc.net
1197463400 Q * Aiken Quit: Leaving
1197463424 M * Pyxcad Hi, could someone give me some clarification about moving a vserver between different hardware ? what are the main requirements ? same kernel or what ?
1197463470 M * daniel_hozac same architecture and kernel series.
1197463483 M * daniel_hozac i.e. i386 and e.g. 2.6.
1197463736 M * Pyxcad are there problems migrating from 32 to 64 bit server?
1197463773 M * Pyxcad or from single to multi processor?
1197463778 Q * FloodServ charon.oftc.net services.oftc.net
1197463796 M * daniel_hozac no.
1197463807 M * daniel_hozac the only problem is 64-bit guest to 32-bit hardware.
1197463813 M * daniel_hozac which just cannot work, ever.
1197463960 M * Pyxcad thank you for your reply. 
1197463974 M * Pyxcad I have to migrate from AMD AthlonŞ XP 2600 to AMD AthlonŞ 64 X2 5000+
1197464077 M * daniel_hozac shouldn't be a problem at all.
1197464265 M * Bertl morning folks!
1197464295 M * daniel_hozac morning Bertl!
1197464378 J * lilalinux ~plasma@dslb-084-058-214-075.pools.arcor-ip.net
1197464433 M * Bertl infowolfe: what kind of messages do you get?
1197464457 M * infowolfe Bertl, it's phreak or Hollow's fault one of them anyway
1197464469 J * berest ~kvirc@A97.sub26.net78.udm.net
1197464474 M * berest hi to all
1197464489 M * berest i have a problem with nmap worked in guest Linux
1197464511 M * berest when i run nmap i get this message "socket troubles in UltraScanInfo::Init: Operation not permitted (1)"
1197464519 M * berest how solve this problem?
1197464527 M * Hollow infowolfe: ?
1197464531 M * Bertl hey berest!
1197464536 M * berest hi
1197464547 M * Bertl berest: simple, don't run layer2 nmap operations in a layer3 guest
1197464566 M * infowolfe Hollow, i'm giving you crap :-p
1197464580 M * berest so...solve this problem inpossible?
1197464581 M * Hollow ehm ...
1197464645 M * Bertl berest: you can give additional capabilities to the guest, but that will give it access to the network interfaces
1197464675 M * berest yes 
1197464683 M * berest but what cap i must give to guest?
1197464710 M * Bertl CAP_NET_RAW or CAP_NET_ADMIN
1197464720 M * berest thx
1197464722 A * infowolfe taps fingers waiting for portage to go through a bunch of old 'binary updates'
1197464743 M * infowolfe Hollow, btw, I'd like to say thanks to you guys for doing so much work making gentoo a lot easier as a guest -and- host
1197464845 M * Hollow infowolfe: you're welcome! unfortunately baselayout-2's future is uncertain since roy left us *sigh*
1197464873 M * Hollow now i have to argue with the base-system morons again
1197464876 M * Bertl berest: http://linux-vserver.org/Capabilities_and_Flags
1197464888 M * infowolfe Hollow, you don't have to argue alone
1197464903 M * infowolfe ask robbat2 for help and he'll gladly give it :-)
1197464932 M * Hollow well, it works good in vservers now, but i'm afraid not for long :)
1197464945 M * infowolfe Hollow, mind a privmsg?
1197464958 M * Hollow no
1197464964 M * Hollow or yes? :P
1197464983 M * infowolfe no means 'yes, please do send me one'
1197464990 M * Hollow okies :)
1197464995 J * Alikus ~alikus@217.150.200.212
1197465180 M * Bertl wb Alikus!
1197465218 M * Alikus Bertl:  hi :)
1197465229 Q * Pyxcad Quit: Pyxcad has no reason
1197465996 M * Bertl @all: it looks like I'm going to speak at PROFOSS in Brussels, Belgium (January the 23rd at 16:00)
1197466021 M * Bertl (i.e. they invited me to give a talk on Linux-VServer)
1197466077 M * infowolfe :)
1197466079 M * infowolfe congrats!
1197466081 M * berest when vserver will support 2.6.24?
1197466097 M * Bertl is it out already?
1197466100 M * infowolfe no
1197466112 M * infowolfe -rc5
1197466130 A * infowolfe wonders why Bertl skipped 2.6.23 entirely
1197466146 M * Bertl I already explained it a bunch of times .. on IRC
1197466165 M * Bertl basically boils down to: 2.6.23 mainline virtualization is quite broken
1197466831 M * infowolfe fair enough
1197467154 J * Infinito argos@200-140-154-162.gnace701.dsl.brasiltelecom.net.br
1197467162 Q * meebey Remote host closed the connection
1197467192 J * meebey meebey@booster.qnetp.net
1197467497 J * metalikus ~alikus@217.150.200.212
1197467497 Q * Alikus Read error: Connection reset by peer
1197467547 Q * shuri Quit: Leaving
1197468247 Q * larsivi Quit: Konversation terminated!
1197468430 J * DavidS cool@helios.uni-ak.ac.at
1197468600 Q * meebey Remote host closed the connection
1197468630 J * meebey meebey@booster.qnetp.net
1197468703 Q * sharkjaw Quit: Leaving
1197469371 Q * pmenier_off Read error: Connection reset by peer
1197469416 J * pmenier_off ~pme@LNeuilly-152-22-72-5.w193-251.abo.wanadoo.fr
1197469475 J * doener ~doener@i577AF8C6.versanet.de
1197469893 Q * doener_ Ping timeout: 480 seconds
1197470999 Q * metalikus Remote host closed the connection
1197471019 J * Alikus ~alikus@217.150.200.212
1197471201 J * FloodServ services@services.oftc.net
1197471218 Q * FloodServ charon.oftc.net services.oftc.net
1197471505 Q * mnemoc Ping timeout: 480 seconds
1197471575 J * FloodServ services@services.oftc.net
1197471682 Q * mick_work Ping timeout: 480 seconds
1197471997 J * mnemoc ~amery@kilo105.server4you.de
1197472191 J * ntrs_ ~ntrs@79.125.244.135
1197472622 Q * ntrs Ping timeout: 480 seconds
1197472665 J * mick_work ~clamwin@adsl-068-157-089-099.sip.bct.bellsouth.net
1197472937 Q * tam Remote host closed the connection
1197473301 J * tam ~tam@gw.nettam.com
1197474298 J * dowdle ~dowdle@scott.coe.montana.edu
1197474379 Q * Infinito Quit: Quitte
1197474413 M * Bertl wb dowdle!
1197474497 A * dowdle drinks coffee and grunts... thanks.
1197475344 Q * gebura Quit: Quitte
1197475764 N * pmenier_off pmenier
1197475764 Q * meebey Remote host closed the connection
1197475794 J * meebey meebey@booster.qnetp.net
1197476169 Q * berest Quit: KVIrc 3.2.4 Anomalies http://www.kvirc.net/
1197476861 J * larsivi ~larsivi@144.84-48-50.nextgentel.com
1197477165 J * Abaddon abaddon@68-71.is.net.pl
1197477229 Q * meebey Remote host closed the connection
1197477259 J * meebey meebey@booster.qnetp.net
1197477599 Q * Alikus Remote host closed the connection
1197478075 Q * WDTY Quit: ChatZilla 0.9.79 [Firefox 2.0.0.11/2007112718]
1197478361 J * undefined ~undefined@adsl-68-94-183-129.dsl.rcsntx.swbell.net
1197478401 J * hparker ~hparker@linux.homershut.net
1197478431 P * undefined 
1197478623 J * ema ~ema@rtfm.galliera.it
1197478673 Q * Julius Quit: Verlassend
1197479090 Q * s0undt3ch Remote host closed the connection
1197479386 J * bonbons ~bonbons@2001:960:7ab:0:20b:5dff:fec7:6b33
1197479791 Q * ema Quit: leaving
1197481388 J * meandtheshell ~sa@85-127-137-224.dynamic.adsl-line.inode.at
1197481425 M * infowolfe Bertl, ping?
1197481432 M * Bertl infowolfe: pong!
1197481444 M * infowolfe is it possible to mount nfs from inside a context?
1197481458 M * Bertl yes, just not advised
1197481500 M * infowolfe can i ask why?
1197481522 M * Bertl yes, mainly because you allow the guest admin to stall your host system
1197481537 M * infowolfe that's fine
1197481545 M * Bertl i.e. do an nfs mount with a third party server, then remove the server, you will hang in the timeout
1197481586 M * infowolfe so i should do the nfs mount from actually inside the context, vs doing it from /etc/vservers/$ctx/fstab?
1197481597 J * zLinux ~zLinux@88.213.33.165
1197481612 M * Bertl you should do the nfs mount from the fstab.remote (ideally)
1197481689 M * infowolfe i figured out that i need sleep
1197481699 M * Bertl :)
1197481707 M * infowolfe the reason why it wasn't bind-mounting from the host box is because i didn't have the path there
1197481906 M * infowolfe Bertl, have you ever explored what your networking quirks do to ipvs-dr realservers?
1197481919 M * infowolfe :-p
1197481927 M * Bertl hmm?
1197481944 M * Bertl what quirks?
1197482017 M * infowolfe well, with the virtualips on lo like they're supposed to be, traffic hits the box with linux-vserver on it and the packets go nowhere
1197482048 M * Bertl hmm? please explain what you think you are seeing?
1197482081 M * infowolfe on a normal machine, incoming packets go from router -> director -> realserver (which has virtualip on lo:0) -> router -> client
1197482105 M * infowolfe on this box, which worked fine before the vserver kernel, it goes router -> director -> realserver
1197482109 M * infowolfe with no return whatsoever
1197482131 M * infowolfe and i'm not sure whether your networking stuff messes with arp or anything along those lines
1197482138 M * Bertl I really doubt that this is Linux-VServer related, you tried with the same config/kernel?
1197482155 M * infowolfe the only difference is your patch
1197482167 M * infowolfe (and the associated config stuffs)
1197482203 M * infowolfe http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.LVS-DR.html that should have a good illustration of packet flow
1197482227 M * Bertl so you can boot the same host with an identically configured (modulo Linux-VServer) kernel, and then LVS on the host behaves differently?
1197482262 M * infowolfe yes
1197482271 M * infowolfe but it's not lvs on the host (this isn't a director)
1197482282 M * infowolfe this is a backend server (realserver in ipvs speak)
1197482290 M * infowolfe the director is the actual load balancer
1197482318 M * Bertl so, you are not even running LVS on the host?
1197482320 M * infowolfe but my loadbalancer shifts all http traffic to this linux-vserver machine (70kpps or so)
1197482342 M * infowolfe i flip the webserver off and everything normalizes
1197482368 J * dowdle_ ~dowdle@scott.coe.montana.edu
1197482371 M * infowolfe so it's got to be some kind of odd interaction with how your networking gets done
1197482380 M * Bertl the web server is the Linux-VServer patched host, and you run the services on the host, yes?
1197482382 Q * faheem__ Ping timeout: 480 seconds
1197482383 A * infowolfe notes to self, ipvs realserver + linux-vserver = no-go
1197482389 Q * pmenier Quit: Konversation terminated!
1197482392 M * infowolfe yes
1197482407 Q * dowdle Ping timeout: 480 seconds
1197482416 M * Bertl then there should be no difference if you have the Linux-VServer patch or not
1197482437 A * infowolfe points to the 'arp problem' as described in that howto
1197482443 M * Bertl note that if you put the services into a guest, it might make a difference
1197482457 M * Bertl arp is not a problem, it is layer 2 and we do not even touch that
1197482471 M * infowolfe somehow the virtual ips that -have- to be bound to loopback are having their traffic not go back out properly
1197482487 M * infowolfe (i'm not even 100% sure they're getting there in one piece, although i'm not seeing anything in dmesg about dropping martians)
1197482489 M * Bertl there is no 'back out' on lo
1197482502 M * infowolfe the traffic isn't coming in on lo ;-)
1197482528 M * Bertl that would mean, that whatever app is sending it there (local app) is not sending
1197482534 Q * DavidS Quit: Leaving.
1197482543 M * infowolfe ipvs-dr rewrites the packet header with the realserver's mac address, leaving all else in place
1197482560 M * infowolfe the realserver then processes the packet, and replies like it would to any other packet
1197482579 M * Bertl sounds good to me, I don't see how that would change
1197482610 M * infowolfe http://www.austintek.com/LVS/LVS-HOWTO/HOWTO/LVS-HOWTO.LVS-DR.html#lvs_dr_arp_problem
1197482714 Q * dna Quit: Verlassend
1197482729 M * Bertl that might be an LVS issue/problem, but I do not see how that would be Linux-VServer related
1197482766 M * infowolfe what does nx_dev_visible do?
1197482782 M * Bertl it hides certain interfaces (information wise) inside a guest
1197482801 M * Bertl (well, it decides which interfaces are visible)
1197482882 M * infowolfe hrm...
1197482898 M * infowolfe maybe you're fixing a bug that is relied upon in order to do the arp tricks
1197482899 M * infowolfe :-p
1197482903 M * infowolfe (always possible)
1197482916 M * Bertl on the host, Linux-VServer is not supposed to change anything
1197482982 N * phedny Guest27
1197482991 J * phedny ~mark@ip56538143.direct-adsl.nl
1197483028 N * dowdle_ dowdle
1197483028 Q * meebey Remote host closed the connection
1197483047 M * Bertl so, if you can create an arp (or whatever) scenario, which changes when used on a Linux-VServer patched kernel (vs. unpatched, same cnfig) we consider it a bug
1197483058 M * Bertl (and of course, it will be fixed asap)
1197483058 J * meebey meebey@booster.qnetp.net
1197483064 J * yarihm ~yarihm@84-75-119-160.dclient.hispeed.ch
1197483076 M * infowolfe Bertl, but finding out where the bug is is the fun part ;-)
1197483080 M * infowolfe if it is in fact a bug
1197483097 M * Bertl it would be a good start to get a minimalistic test scenario :)
1197483129 J * Julius ~julius@p57B25942.dip.t-dialin.net
1197483143 M * Bertl wb Julius!
1197483145 Q * Guest27 Ping timeout: 480 seconds
1197483146 M * infowolfe which unfortunately is not very possible due to the whole purpose of having the setup 'up'
1197483174 M * Bertl if you assume it is arp related, a simple arp/no-arp setup should expose the issue, no?
1197483188 M * Bertl (especially as LVS on the host is not relevant as you said)
1197483292 M * infowolfe it's the fact that we're basically tricking the host into allowing replies on an ip that is bound to lo:0 without it being bound to a public interface
1197483331 M * infowolfe i must sleep though
1197483335 M * infowolfe let's talk tomorrow about it
1197483339 M * Bertl as I said, if it works on an unpatched kernel, I do not see why it shouldn't work on a patched one :)
1197483356 M * Bertl k, have a good sleep
1197483405 J * JonB ~NoSuchUse@kg1-98.kollegiegaarden.dk
1197483740 J * faheem ~faheem@152.16.8.94
1197483751 M * Bertl wb faheem!
1197484542 J * DoberMann ~james@cap31-6-88-180-72-76.fbx.proxad.net
1197484886 Q * DoberMann Quit: brb
1197484964 J * DoberMann ~james@cap31-6-88-180-72-76.fbx.proxad.net
1197485083 N * DoberMann DoberMann[PullA]
1197485084 Q * meebey Remote host closed the connection
1197485114 J * meebey meebey@booster.qnetp.net
1197486137 J * cedric ~cedric@rny93-2-82-66-66-30.fbx.proxad.net
1197487968 Q * DoberMann[PullA] Remote host closed the connection
1197487981 J * DoberMann[PullA] ~james@cap31-6-88-180-72-76.fbx.proxad.net
1197488039 Q * lilalinux Remote host closed the connection
1197489019 Q * Abaddon Quit: leaving
1197489148 Q * meebey Remote host closed the connection
1197489178 J * meebey meebey@booster.qnetp.net
1197489709 J * ema ~ema@rtfm.galliera.it
1197491475 Q * JonB Quit: This computer has gone to sleep
1197491793 Q * bonbons Ping timeout: 480 seconds
1197492257 Q * mick_work Remote host closed the connection
1197492350 J * mick_work ~clamwin@adsl-068-157-089-099.sip.bct.bellsouth.net
1197492423 Q * AStorm Ping timeout: 480 seconds
1197492487 Q * mick_work Remote host closed the connection
1197492493 J * AStorm ~astralsto@chello089077114002.chello.pl
1197492558 Q * larsivi Quit: Konversation terminated!
1197493050 J * Aiken ~james@ppp121-45-246-228.lns2.bne4.internode.on.net
1197493749 Q * meebey Remote host closed the connection
1197493779 J * meebey meebey@booster.qnetp.net
1197494010 Q * meandtheshell Quit: Leaving.
1197494087 Q * infowolfe Ping timeout: 480 seconds
1197494316 Q * ema Quit: leaving
1197494495 J * JonB ~NoSuchUse@kg1-98.kollegiegaarden.dk
1197495051 Q * hparker Quit: Quit
1197495106 J * Abaddon abaddon@68-71.is.net.pl
1197495176 Q * nebuchadnezzar Read error: Connection reset by peer
1197495280 J * nebuchadnezzar ~nebu@zion.asgardr.info
1197495470 J * atterdag ~atterdag@c-12d2e455.43-40-64736c10.cust.bredbandsbolaget.se
1197495647 Q * JonB Quit: This computer has gone to sleep
1197495664 M * Bertl welcome atterdag!
1197495924 Q * cedric Quit: cedric
1197495934 J * hparker ~hparker@linux.homershut.net
1197495978 Q * meebey Remote host closed the connection
1197496008 J * meebey meebey@booster.qnetp.net
1197496305 J * edeschen ~edeschen@proxy-sjc-2.cisco.com
1197496359 M * edeschen Hi daniel, are you around?
1197496367 M * Bertl wb edeschen!
1197496380 M * edeschen Hi Bertl
1197496578 P * Q_ 
1197496738 J * shuri ~shuri@64.235.209.226
1197496862 M * edeschen Hey Bertl, I was asking a question yesterday about "vserver stop" and init-style=plain on the channel. daniel_hozac was kind enough to help me out. The issue I was seeing was about "vserver stop" timing out (even though I had an empty vserver - no application, just simple install).
1197496897 M * edeschen daniel asked me about the guest distro which I told him was custom made (I used the vserver build skeleton)
1197496914 M * edeschen then he suggested to use -m yum and see if I still had the issue
1197496924 M * Bertl plain means you have a guest init running, right?
1197496931 M * edeschen correct
1197496945 M * edeschen I have /sbin/init
1197496950 M * Bertl does your guest init get the signal for shutting down (and act upon it)?
1197496963 M * edeschen I built this morning a new guest with the --initstyle option to plain
1197496988 M * edeschen that had for consequences to put the init/style = plain and create the /dev/initctl correctly
1197497010 M * edeschen and I changed the /etc/inittab default level and I see that it picks it up
1197497024 M * edeschen so the /sbin/init in the guest seems to be called properly
1197497044 M * edeschen daniel was asking what was in the /etc/init.d/halt yesterday
1197497061 M * edeschen so today, with the new guest built with  the -m yum option
1197497115 M * edeschen I see: exec killall5 -15
1197497159 M * edeschen he was referring that the shutdown sequence should call sys_reboot(HALT)
1197497177 M * edeschen so I'm wondering if the killall5 is invoking this syscall
1197497184 M * edeschen or I'm missing something here
1197497262 M * edeschen and I put a log statement in the /etc/init.d/halt and I see this in the log when doing "vserver stop"
1197497287 M * edeschen so init (inside the guest) get notified from the host upon "vserver stop"
1197497317 M * edeschen I dont see the /etc/rc0.d/K* getting called though
1197497462 M * edeschen I also tried to invoke "/etc/init.d/halt" from INSIDE the vserver. When doing so, I get kicked out of the vserver but a vserver-stat still show the vserver up.
1197497514 Q * meebey Remote host closed the connection
1197497544 J * meebey meebey@booster.qnetp.net
1197497568 M * Bertl edeschen: sounds like a malfunction of your guest's init
1197497614 M * Bertl edeschen: is your guest's inittab configured properly?
1197498002 Q * Julius Quit: Verlassend
1197498563 Q * FireEgl Ping timeout: 480 seconds
1197498568 M * edeschen Bertl: I think so, the mingetty are all commented out, the l? are all present and point to /etc/rc.d/rc (which is present on the file system). id:3:initdefault:
1197498608 M * edeschen so as far as I can tell the /etc/inittab file seems to be correct, anything special I should be looking at?
1197498614 M * Bertl are they executed? do they work and exit successfully?
1197498633 M * Bertl try enabling some logging/debug for init
1197498666 Q * meebey Remote host closed the connection
1197498698 M * edeschen ok, I'll try enabling some debug for init
1197498702 J * meebey meebey@booster.qnetp.net
1197498927 Q * tam Remote host closed the connection
1197499096 J * FireEgl FireEgl@Sebastian.Tcldrop.US
1197499298 J * tam ~tam@gw.nettam.com
1197501331 M * Bertl okay, off to bed now .. have a good one everyone!
1197501378 N * Bertl Bertl_zZ
1197502053 J * dna ~dna@223-222-dsl.kielnet.net
1197502684 M * daniel_hozac edeschen: add halt -f there.
1197502711 Q * dna Quit: Verlassend