On Tue, 16 Mar 2010 08:49:31 -0400, Eric Cooper <e...@cmu.edu> wrote: > On Fri, Mar 12, 2010 at 12:31:58PM -0500, Micah Anderson wrote: > > Approx used to honor TMP and TMPDIR environment variables, but I > > believe that when #451768 was uploaded, this stopped working. > > > > It is important to be able to specify alternative temporary > > directories. I cannot run the daily approx cronjob now because my /tmp > > fills up, and I have no way of specifying an alternative location. :( > > You're correct that approx currently ignores TMP and TMPDIR so that it > works OK with pam-tmpdir. I'm sorry that this is inconveniencing you. > > I think you can work around this by running the approx cron jobs in a > chroot with a bigger tmp:
This wont work because I am already running approx in a chroot (linux-vserver containers which do not allow the chroot() kernel capability). > Please let me know if this is a feasible workaround for you (and if > so, whether I can lower this to a normal or wishlist priority bug). Sorry, it wont work for me :( Everything else seems to honor TMP/TEMPDIR, what is the purpose of going against that convention? m
pgpWrDhQ4fbZg.pgp
Description: PGP signature
