ltsp-build-client and ltsp-update-image fails if inetd.conf is not cleared
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ltsp (Ubuntu) |
Fix Released
|
Undecided
|
Oliver Grawert |
Bug Description
When I run ltsp-build-client or ltsp-update-image, both fails if
the nbdrootd line for port 2000 is not removed.
This is not a big showstopper for me since quick jab with emacs
will help me around it, but I can imagine teachers without
much unix experience not knowing anything about neither
inetd or how to configure the same.
And yes, I am running the plain vanilla inetd that comes
standard with *buntu, no xinetd or anything fancy.
Well according to /etc/init.d it is actually from openbsd.
It may be a good thing updating inetd, but beware,
when running thin clients we do expect user to have
complex needs and many may not be served well
with the stock inetd package and I would rather see
that the tools create images and things like the name
implies rather then messing with config files that should
be left to the system manager to handle.
Though I had other problems earlier, I did not run into
this particular issue until running an upgrade yesterday.
Best,
R.R.
Changed in ltsp: | |
status: | Fix Released → In Progress |
whats the error message and whats your ltsp version ?
the error message was turned into a warning with the 5.0.26 upload (see below)
ltsp (5.0.26) gutsy; urgency=low
[Oliver Grawert <email address hidden>]
* new udeb postinst (and new template) added, fixes (LP: #121547)
we have full progress reporting in the installer now :)
* added option --skipimage to ltsp-build-client to supress ltsp-update-image
execution in d-i (we run it separately in the udeb)
* its not an error if the port is set in inetd.conf.
...