[Pkg-ltsp-devel] Bug#765443: ltsp-server: Unset variables set by libpam-tmpdir in ltsp-chroot?

[Vagrant Cascadian]

On 2014-10-15, Petter Reinholdtsen wrote:
> When using libpam-tmpdir on the LTSP server and then calling
> 'ltsp-chroot' to do operations in the LTSP chroot, the temp directory
> variables are inherited and causing 'apt-get upgrade' (because of
> postinst scripts using the temp directory variables) etc. to fail
> because the temporary directory do not exist.  Can ltsp-chroot be
> changed to unset the temp directory variables if they point to a
> non-existing directory?
>
> These are the variables set by libpam-tempdir:
>
>   TMPDIR=/tmp/user/1000
>   TEMP=/tmp/user/1000
>   TEMPDIR=/tmp/user/1000
>   TMP=/tmp/user/1000

I'm not sure what to make of this one, honestly.

Creating the directories would be error prone and likely to leave cruft
behind.

Unsetting the variables seems to circumvent libpam-tmpdir entirely,
though would be simple enough. I guess I lean towards this...

Conditionally checking for the presence of the dir and unsetting each
variable individually seems only slightly less bad that blindly
unsetting the variables, and a lot more code...


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ltsp-devel/attachments/20141015/ded936b7/attachment.sig>