Re: An arbitrarily sized /tmp does not fit all

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/20/2012 11:17 PM, Matthew Miller wrote:
On Thu, Dec 20, 2012 at 01:03:37PM -0800, Chuck Forsberg WA7KGX N2469R wrote:
For whatever reason Anaconda generates a separate file system for /tmp
using an arbitrary size.  One one machine it is about 4GB, causing Brasero
to fail on larger jobs.  Meanwhile there is some 30GB unused in the root
filesystem.
If /tmp is no longer part of / then its size should be easily adjustable.


Check the filesystem -- it's in RAM by default using tmpfs, and tmpfs
defaults to a size of half of physical ram. To disable and go back to haivng it be part of /,

   sudo systemctl mask tmp.mount

To change the limit while leaving it in-ram, I assume you'd put the desired
size in the Options line in the systemd tmp.mount file, but there may be a
better way.

I believe the argument is that if Brasero needs more space, /var/tmp would
be a better place.

This is a fine example of what a facepalm (to put it mildly) the whole /tmp-on-tmpfs is, really...

	- Panu -

--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test



[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux