Serious flaw in virtual-ltsp scripts

--===============1690574144628411239==
Content-Type: multipart/alternative; boundary="0000000000007bc6340577814f16"

--0000000000007bc6340577814f16
Content-Type: text/plain; charset="UTF-8"

Hi,

I noticed recently that whatever I install on the ltsp-server
ends up running on the ltsp-clients as well (with chrootless mode).
Actually this is a well-known fact, but I didn't think there was
anything wrong with it, until I realized that apache2, and tomcat,
and mysql were running on the client too, eating up a lot of ram!

As a workaround I changed the order of scripts so that the image
of the ltsp-client is generated as soon as possible, and then we
proceed with the other installations and configurations, with
guacamole, etc.

However this solution has the drawback that afterwards you cannot
install any more packages on the client image (if you need to).
The only way is to rebuild the ltsp-server from scratch, and this takes
a lot of time (about one hour), since lots of things have to be
downloaded and installed (sometimes even compiled from source).

Is it possible to unpack the image of a chrootless client to a directory,
to chroot to this directory and install any additional packages, and
then to pack it back again? This could be much faster than rebuilding
the whole server from scratch (and also more elegant).

Thanks,
Dashamir

--0000000000007bc6340577814f16
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I noticed recently that whatever I =
install on the ltsp-server</div><div>ends up running on the ltsp-clients as=
 well (with chrootless mode).</div><div>Actually this is a well-known fact,=
 but I didn&#39;t think there was</div><div>anything wrong with it, until I=
 realized that apache2, and tomcat,</div><div>and mysql were running on the=
 client too, eating up a lot of ram!</div><div><br></div><div>As a workarou=
nd I changed the order of scripts so that the image</div><div>of the ltsp-c=
lient is generated as soon=C2=A0as possible, and then we</div><div>proceed =
with the other installations and configurations, with</div><div>guacamole, =
etc.</div><div><br></div><div>However this solution has the drawback that a=
fterwards you cannot</div><div>install any more packages on the client imag=
e (if you need to).</div><div>The only way is to rebuild the ltsp-server fr=
om scratch, and this takes</div><div>a lot of time (about one hour), since =
lots of things have to be</div><div>downloaded and installed (sometimes eve=
n compiled from source).</div><div><br></div><div>Is it possible to unpack =
the image of a chrootless client to a directory,</div><div>to chroot to thi=
s directory and install any additional packages, and</div><div>then to pack=
 it back again? This could be much faster than rebuilding</div><div>the who=
le server from scratch (and also more elegant).</div><div><br></div><div>Th=
anks,</div><div>Dashamir</div><div><br></div></div>

--0000000000007bc6340577814f16--


--===============1690574144628411239==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============1690574144628411239==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

--===============1690574144628411239==--