1443398623 Q * fstd Remote host closed the connection
1443399614 Q * FireEgl Quit: Leaving...
1443401039 J * fstd ~fstd@xdsl-87-78-14-5.netcologne.de
1443413489 J * fstd_ ~fstd@xdsl-84-44-221-169.netcologne.de
1443413631 Q * fstd Ping timeout: 480 seconds
1443413631 N * fstd_ fstd
1443415691 Q * eyck Ping timeout: 480 seconds
1443415928 J * eyck ~eyck@u28n61.nowanet.pl
1443419023 J * aj__ ~aj@nl8x.mullvad.net
1443422697 J * Ghislain ~aqueos@adsl1.aqueos.com
1443424315 M * Bertl_oO off to bed now ... have a good one everyone!
1443424316 N * Bertl_oO Bertl_zZ
1443424874 Q * aj__ Ping timeout: 480 seconds
1443426206 J * aj__ ~aj@2001:6f8:1337:0:78e5:d216:5b00:f61f
1443432160 J * nikolayK ~nkichukov@199.91.137.248
1443433534 J * Gremble ~Gremble@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net
1443433938 Q * aj__ Ping timeout: 480 seconds
1443436280 Q * kwork Quit: No Ping reply in 180 seconds.
1443436413 J * kwork ~user@bnc.ee
1443437234 J * aj__ ~aj@nl12x.mullvad.net
1443437800 Q * aj__ Remote host closed the connection
1443440603 Q * Aiken Remote host closed the connection
1443441561 Q * fstd Remote host closed the connection
1443441572 J * fstd ~fstd@xdsl-87-78-184-232.netcologne.de
1443442896 Q * Hunger- Ping timeout: 480 seconds
1443444015 Q * Jb_boin Remote host closed the connection
1443444021 J * Jb_boin ~dedior@proxad.eu
1443446509 Q * Gremble Quit: I Leave
1443449987 Q * tunka Quit: Leaving
1443455363 N * Bertl_zZ Bertl
1443455365 M * Bertl morning folks!
1443456071 J * bonbons ~bonbons@2001:a18:204:1501:a0f3:5a5:7d0f:2008
1443456283 Q * nikolayK Quit: Leaving
1443467221 J * csh-harmful ~unknown__@174.142.247.150
1443467406 M * csh-harmful hi! Does anyone have positive expirience running systemd inside vserver instance ?
1443467521 J * derjohn_mob ~aj@p50990e60.dip0.t-ipconnect.de
1443467557 M * Bertl I don't think so ... systemd is very "intrusive" and wants to control everything on the hardware or kernel level
1443467578 M * Bertl i.e. it is not designed to be run inside containers
1443467799 M * csh-harmful There is no easy way to submit 'stub' interfaces to systemd to shut it off while retaining only process supervision functionality ?
1443468033 M * Bertl only Lennart knows ...
1443468056 M * Bertl but if you find out a way to use it properly, please let us know
1443468865 M * daniel_hozac there is https://wiki.freedesktop.org/www/Software/systemd/ContainerInterface/
1443468884 M * daniel_hozac but i'm not sure if anyone has succeeded in getting that working inside a guest, since it still wants to do a lot.
1443469467 M * Bertl I think it is more for running systemd inside a systemd container
1443471306 Q * bonbons Quit: Leaving
1443471875 J * Aiken ~Aiken@d63f.h.jbmb.net
1443473011 Q * ensc|w_ Remote host closed the connection
1443473021 J * ensc|w ~ensc@62.153.82.27
1443475536 M * Ghislain it does not work it require the admin privilege in the container
1443475564 M * Ghislain well it surely works but then your vserver guest has rigth on the host so...
1443475637 M * Ghislain systemd is made for VM not containers
1443475660 M * Ghislain it wants to be the container system and run everything in his cgroup and manage ressources
1443475726 M * Ghislain so you cannot have 2  system doing the same thing, this is why systemd anoy, it want to be the windows of linux, next step will be a windowing systemd daemon to replace X
1443475803 M * Ghislain the idea is good but the complete lack of possibility to choose what part you want and what you do not and also the fact that it is linux only is a real issue for the unix community IMHO
1443480908 M * Bertl off for a nap ... bbl
1443480910 N * Bertl Bertl_zZ
1443482567 Q * Ghislain Quit: Leaving.
1443484760 Q * fstd Remote host closed the connection
1443484772 J * fstd ~fstd@xdsl-84-44-146-92.netcologne.de