On Fri, Nov 30, 2007 at 07:26:45PM -0800, [EMAIL PROTECTED] wrote: > 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 agree. Always disregarding them is probably worse.
> 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. > I'm not sure. I have also found that dchroot has the exact same problem, as does chroot. Incidentally, if something is called with sudo, you have the benefit that sudo mostly sanitizes the environment. Perhaps this is something that can be solved in concert with the other packages that share the problem. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
