ltsp scripts dont work properly if chroot basedir is a symlink

Bug #151503 reported by Oliver Grawert
Affects Status Importance Assigned to Milestone
ltsp (Ubuntu)
Fix Released

Bug Description

if the ltsp chroot basedir (usually /opt/ltsp) is a symlink, most of the ltsp maintenance scripts fail to work properly. adding a trailing / in the various find commands in the scripts seems to help.

Related branches

Oliver Grawert (ogra)
description: updated
Changed in ltsp:
importance: Undecided → Wishlist
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ltsp - 5.0.40~bzr20080212-0ubuntu4

ltsp (5.0.40~bzr20080212-0ubuntu4) hardy; urgency=low

  * make sure the right proxy line is set in the chroot, thanks
    to stephane graber for that fix (LP: #213927)
  * make acpid [ i386 amd64 ] only dependency, since its not not available on ppc
    (LP: #213014, LP: #199747)
  * fix interpreter line (LP: #196706)
  * make sure resolv.conf is available in the chroot (LP: #72482)
  * merge fix for dhcp port handling, thanks to Michael Haas, (LP: #198356)
  * we only tell users with nfs-kernel-server installed that they need to
    update /etc/exports (LP: #198915)
  * fix kiosk plugin to use the right package names (LP: #163278, LP: #212738)
  * fix hardcoded path in ltsp-update-image and quiten down noisy rm commands
    (LP: #198157)
  * make sure the ltsp-update-* scripts operate on symlinked dirs (LP: #151503)
  * add final updates for mythbuntu plugin and drop accidentially included
    patch file from debian/extra-plugins (LP: #212550)

 -- Oliver Grawert <email address hidden> Tue, 08 Apr 2008 15:03:51 +0200

Changed in ltsp:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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