[Pkg-ltsp-devel] Bug#451878: Bug#451878: /usr/sbin/ltsp-build-client: Doesn't properly clean up environment

[vagrant at freegeek.org]

On Sun, Nov 18, 2007 at 09:43:40PM -0500, Roberto C. Sanchez wrote:
> I use pam_tmpdir on my system.  So, for example, root has this in his
> environment:
> 
> TMP=/tmp/user/0
> TMPDIR=/tmp/user/0
> 
> One or both of those values are sticking around when ltsp-build-client
> is called, resulting in this failure:
> 
> Running depmod.
> Finding valid ramdisk creators.
> Using mkinitramfs-kpkg to build the ramdisk.
> mktemp: cannot make temp dir /tmp/user/0/mkinitramfs_W13305: No such file or directory
> mkinitramfs-kpkg failed to create initrd image.
> 
> It looks like the call to mktemp is making use of one of the variables.
> Of course, since the chroot for the client created in /opt/ltsp is
> clean, there is no user/0 directory below /tmp.

indeed.

do you propose we change ltsp-build-client to ignore TMP and TMPDIR?
then any non-chrooted calls ltsp-build-client makes will disregard the
user's TMP/TMPDIR setting, which doesn't seem right either.

i guess i could implement this as part of the long-lost ltsp-chroot
idea, which is a chroot wrapper that ltsp-build-client calls, and could
set and unset some environment variables.

live well,
  vagrant