ltsp-client-setup init script should source lts.conf

Bug #259790 reported by Mario Limonciello
4
Affects Status Importance Assigned to Milestone
ltsp (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

The contents of /etc/lts.conf should propogate into the resultant client systems. The issue I run into personally is that I don't want my fstab updated on every boot. I set this in the lts.conf of the main chroot, run ltsp-update-image.

I expect that it doesn't get updated on every boot then. It still does however. This is because /etc/init.d/ltsp-client-setup doesn't source /etc/lts.conf. It only sources /etc/default/ltsp-client-setup. I think that lts.conf should also be sourced since that's where CONFIGURE_FSTAB is defined.

Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

In my Lucid setup, ltsp-client-setup sources /usr/share/ltsp/ltsp-init-common, which in turn sources /usr/share/ltsp/ltsp_config, which sources lts.conf:
# Read in lts.conf entries.
if [ -f /etc/lts.conf ]; then
    eval $(getltscfg -a) || true
fi

Are you still experiencing the problem?

Changed in ltsp (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ltsp (Ubuntu) because there has been no activity for 60 days.]

Changed in ltsp (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.