1327363930 Q * Aiken Ping timeout: 480 seconds
1327364127 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f
1327366944 Q * dowdle 
1327381673 Q * jrklein Ping timeout: 480 seconds
1327390262 J * derjohn_mob ~aj@d046101.adsl.hansenet.de
1327390306 J * fisted_ ~fisted@xdsl-87-78-217-31.netcologne.de
1327390523 Q * fisted Ping timeout: 480 seconds
1327390563 J * Marbug ~Marbug@83.101.67.3
1327391158 J * ghislain ~AQUEOS@adsl2.aqueos.com
1327391243 Q * derjohn_mob Ping timeout: 480 seconds
1327392229 Q * micah synthon.oftc.net graviton.oftc.net
1327392229 Q * WMP synthon.oftc.net graviton.oftc.net
1327392229 Q * FIChTe synthon.oftc.net graviton.oftc.net
1327394818 M * Bertl off to bed now ... have a good one everyone!
1327394834 N * Bertl Bertl_zZ
1327395382 Q * ensc|w Remote host closed the connection
1327395390 J * ensc|w ~ensc@www.sigma-chemnitz.de
1327396553 J * micah ~micah@micah.riseup.net
1327396553 J * FIChTe ~fichte@bashpipe.de
1327396553 J * WMP ~oftc@auburn.sored.pl
1327403229 J * petzsch ~markus@dslb-088-075-122-206.pools.arcor-ip.net
1327403689 Q * petzsch Quit: Leaving.
1327406187 Q * Aiken Remote host closed the connection
1327408723 J * petzsch ~markus@dslb-088-075-122-206.pools.arcor-ip.net
1327410347 Q * petzsch Quit: Leaving.
1327413109 T * * http://linux-vserver.org/ |stable 2.2.0.7, exp 2.3.0.36.38, grsec 2.3.0.36.28|util-vserver-0.30.216-pre2914| 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.
1327413109 T * ChanServ -
1327414304 J * jeroen__ ~jeroen@095-097-051-172.static.chello.nl
1327418480 N * ensc Guest356
1327418490 J * ensc ~irc-ensc@p54ADF4C3.dip.t-dialin.net
1327418879 J * petzsch ~markus@dslb-088-075-122-206.pools.arcor-ip.net
1327418902 Q * Guest356 Ping timeout: 480 seconds
1327419269 N * Bertl_zZ Bertl
1327419273 M * Bertl morning folks!
1327420982 J * click click@ice.vcon.no
1327421026 J * ryker ~jalberts@c-67-176-243-86.hsd1.in.comcast.net
1327421337 J * dowdle ~dowdle@scott.coe.montana.edu
1327421729 Q * petzsch Quit: Leaving.
1327423558 J * petzsch ~markus@dslb-088-075-122-206.pools.arcor-ip.net
1327424857 J * bonbons ~bonbons@2001:960:7ab:0:788a:cbcb:2c85:ffa4
1327427720 Q * hparker Remote host closed the connection
1327428377 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647
1327429937 J * clopez ~clopez@155.99.117.91.static.mundo-r.com
1327429958 M * clopez hi
1327432658 M * clopez i have a question... is safe to copy one vserver from one host to another with dd (the full filesystem)?
1327432676 J * BenG ~bengreen@5e0f1636.bb.sky.com
1327432698 M * clopez supossing the vserver is stopped and the rootfs of it unmounted
1327432789 Q * BenG 
1327432847 M * daniel_hozac i suppose.
1327432853 M * daniel_hozac typically one would use rsync though.
1327433031 J * BenG ~bengreen@5e0f1636.bb.sky.com
1327433198 M * clopez i answer myself.. is not: you have to change the xids with 
1327433207 M * clopez chxid -c nex_context -R /mount/point
1327433233 M * clopez or keep the same context (which would be difficult since you will have vservers with same context in the new machine)
1327433236 M * daniel_hozac only if it changes xids, which it really shouldn't for a move.
1327433288 M * clopez for example i am moving a vserver with context 40030, and in the new machine i have another server with this context 
1327433295 M * clopez so i need to change the context for the moved server
1327433366 M * clopez and i was getting.. unable to start vserver (unable to run /sbin/init: permission denied) because the xid of the rootfs was different from the context that i changed
1327433410 M * daniel_hozac if you have a filesystem per guest, why are you using tagging?
1327433543 M * clopez is not needed?
1327433678 M * daniel_hozac no.
1327433845 M * Bertl clopez: the idea behind tagging is that you can tell files apart (i.e. belonging to a context) on a shared filesystem
1327433862 M * Bertl no filesystem sharing, no point in using filesystem tagging :)
1327434057 M * clopez and there is a point in using the "tag" option when mounting the filesystem for the vserver or is overkill?
1327434187 M * Bertl as I said, you can do that, but there is no real point as all files will be tagged with the same tag
1327434456 M * clopez I think that i am a bit lost about tagging.. then for what is useful this feature? ... perhaps is for avoid escaping the chroot?
1327434504 J * fisted ~fisted@xdsl-87-78-212-217.netcologne.de
1327434537 M * daniel_hozac 20:37 < Bertl> clopez: the idea behind tagging is that you can tell files apart (i.e. belonging to a context) on a shared filesystem
1327434610 M * DelTree 32
1327434614 M * DelTree oops...
1327434631 Q * fisted_ Ping timeout: 480 seconds
1327434647 M * clopez mmm.. is a way to differentiate files belonging to different vservers on one filesystem?
1327434786 M * daniel_hozac yes
1327434786 M * Bertl yep, that's what tags are for
1327435267 M * clopez and there is any security implications of not using tags on a shared filesystem with vservers if each vserver is on their own dir (ex: /var/lib/vservers/xxx) ?
1327435296 Q * BenG Quit: I Leave
1327435566 M * daniel_hozac only if you let the guests share files on that filesystem.
1327435696 J * derjohn_mob ~aj@d074099.adsl.hansenet.de
1327436346 M * clopez ok, i see
1327436367 M * clopez thanks a lot for this master lesson :D
1327436397 M * clopez so i guess i should be doing things better without tags since i have a lvm filesystem for each vserver
1327436634 M * Bertl probably simpler to forget about tagging then
1327438106 Q * clopez Ping timeout: 480 seconds
1327441486 Q * hparker Remote host closed the connection
1327441889 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f
1327442083 Q * bonbons Quit: Leaving
1327443022 Q * Marbug Ping timeout: 480 seconds
1327443093 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647
1327445814 Q * sannes Remote host closed the connection
1327446030 Q * petzsch Quit: Leaving.
1327446695 Q * ghislain Quit: Leaving.