[Bug 1008618] Re: ltsp-cluster SERVER variable is overwritten by ltsp_config file.
Marc Gariépy
gariepy.marc at gmail.com
Fri Jun 8 14:58:32 UTC 2012
** Description changed:
- when booting a ltsp-cluster thin client I am unable to get my
- configuration because the variable SERVER is overwritten by the file
- /var/cache/ltsp/ltsp_config.
+ [Impact]
+ when booting a ltsp-cluster thin client I am unable to get my configuration because the variable SERVER is overwritten by the file /var/cache/ltsp/ltsp_config.
So we need to rename SERVER to CC_SERVER in getltscfg-cluster for it to
work properly.
+
+ [test case]
+ configure your chroot to use ltsp-cluster.
+ run getltscfg-cluster -a
+
+ the server that it tryed to contact is the nbd-server
+
+ [regression potential]
+ None : The variable for the ltsp-cluster is changed to CC_SERVER in the script and configuration for ltps-cluster.
+
the patch can be found here:
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2303
thanks
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/1008618
Title:
ltsp-cluster SERVER variable is overwritten by ltsp_config file.
Status in Linux Terminal Server Project:
Fix Committed
Status in “ltsp” package in Ubuntu:
Triaged
Status in “ltsp” source package in Precise:
In Progress
Status in “ltsp” source package in Quantal:
Triaged
Bug description:
[Impact]
when booting a ltsp-cluster thin client I am unable to get my configuration because the variable SERVER is overwritten by the file /var/cache/ltsp/ltsp_config.
So we need to rename SERVER to CC_SERVER in getltscfg-cluster for it
to work properly.
[test case]
configure your chroot to use ltsp-cluster.
run getltscfg-cluster -a
the server that it tryed to contact is the nbd-server
[regression potential]
None : The variable for the ltsp-cluster is changed to CC_SERVER in the script and configuration for ltps-cluster.
[development fix]
I know this section is deprecated but it's actually relevant in this case ;)
The fix hasn't hit quantal yet because of some massive packaging rework going on with LTSP to try and bring us in sync with Debian. I can guarantee that we will have a new upstream release in quantal that will include this fix. ETA is of a couple of weeks.
the patch can be found here:
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2303
thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ltsp/+bug/1008618/+subscriptions
More information about the foundations-bugs
mailing list