Bug#669726: release-notes: Please document tmpfs filesystem changes for wheezy
Hi,
On Sat, Mar 30, 2013 at 11:50:11AM +0900, Charles Plessy wrote:
> Le Wed, Mar 27, 2013 at 07:54:13AM +0900, Charles Plessy a écrit :
> > Le Wed, Mar 27, 2013 at 01:45:35AM +0900, Osamu Aoki a écrit :
> > > >
> > > > 2.2.6. Temporary filesystems
...snip
> > > This should be more like:
> > >
> > > > * Applications which create excessively large temporary files
> > > > always only in /tmp while not honoring $TMPDIR may
> > > > cause /tmp to run out of free space. Such applications should not
> > > > force to use /tmp, and require fixing. Please consider filing a bug
> > > > report against the application in question if you experience such
> > > > an occurrence.
> >
> > Thanks, I will adjust the patch.
>
> I attached an updated patch were I changed the paragraph above and also
> corrected a typo where /etc/default/tmpfs was substituted by /etc/default/rcS
> in the summary table.
>
> For libpam-tmpdir, I am not able to write something by myself. There is no
> on-line documentation, and from I read in the README, I do not understand why
> one would like to have /tmp on /tmpfs and then globally set TMPDIR to point to
> another directory so that /tmp is not used.
In short, now think it is better not to mention libpam-tmpdir. That is
why I did not mention it now. So your patch seems good for me.
Osamu
PS: My rationale to mention $TMPDIR was to avoid excessive bug reports
on presumably existing DVD-burner programs which write huge data on /tmp
but they honor redirection of data via $TMPDIR. At least this $TMPDIR
offers a simple work around hook functionality for such programs.
The environment variable $TMPDIR can be set via several methods. I
thought libpam-tmpdir is just one of them. Now that I rethink, it may
not be the best solution since it may interfere too much as you
mentioned.
Reply to: