LinuxQuestions.org

LinuxQuestions.org (http://www.linuxquestions.org/questions/index.php)
-   Slackware (http://www.linuxquestions.org/questions/forumdisplay.php?f=14)
-   -   Managing Slackware - /tmp directory (http://www.linuxquestions.org/questions/showthread.php?t=4175444743)

trainee 01-08-2013 06:42 PM

Managing Slackware - /tmp directory
 
My /tmp direcotry contains a lot of directory with strange name like lu6qsnb[a-z]... and files like virtuoso-*.ini

Can you tell me what are those files doing, why are they created, and is it safe to remove them?

Thanks in advance.

allend 01-08-2013 06:58 PM

The virtuoso-*.ini are created by virtuoso when running KDE, of which one will be relevant while the KDE session is running. Not sure about the lu* files.
They can all be safely deleted. Anything in /tmp is a temporary file that can be regenerated if required.

trainee 01-08-2013 07:45 PM

Thanks. I just delete all those and everything seems fine.

Habitual 01-08-2013 09:37 PM

I use tmpwatch myself. ;)

dugan 01-08-2013 10:28 PM

A lot of Slackers put the following line in /etc/fstab:

Code:

tmpfs            /tmp            tmpfs      defaults        0  0
That mounts /tmp on a RAM drive, so that it's cleared every boot.

Uzuki 01-10-2013 11:54 AM

what is the diferences between
Code:

tmpfs            /tmp            tmpfs      defaults        0  0
and
Code:

tmpfs            /dev/shm        tmpfs      defaults        0  0

dugan 01-10-2013 02:22 PM

First first mounts /tmp on a RAM drive. The second mounts /dev/shm on a RAM drive. I have both lines in my fstab.

Habitual 04-30-2013 01:43 PM

Quote:

Originally Posted by dugan (Post 4865864)
A lot of Slackers put the following line in /etc/fstab:

Code:

tmpfs            /tmp            tmpfs      defaults        0  0

Already present and I'm confident that I did not alter this file...
Maybe Pat really does know what's best for me. :)

ruario 04-30-2013 02:47 PM

Quote:

Originally Posted by Habitual (Post 4942096)
Already present and I'm confident that I did not alter this file...
Maybe Pat really does know what's best for me. :)

That line isn't preset by the installer. Perhaps you are reading the /dev/shm line?

Habitual 04-30-2013 03:55 PM

Quote:

Originally Posted by ruario (Post 4942128)
That line isn't preset by the installer. Perhaps you are reading the /dev/shm line?

Waaaaaaay too many consoles open today...
You are correct, of course:
Code:

tmpfs            /dev/shm        tmpfs      defaults        0  0

ruario 04-30-2013 04:03 PM

@trainee: You might find this useful http://docs.slackware.com/howtos:gen...ree_your_space

rkelsen 04-30-2013 10:15 PM

Quote:

Originally Posted by dugan (Post 4865864)
A lot of Slackers put the following line in /etc/fstab:

Code:

tmpfs            /tmp            tmpfs      defaults        0  0
That mounts /tmp on a RAM drive, so that it's cleared every boot.

This.

And then you can make your web browser store its cache there... ;)

Martinus2u 05-01-2013 05:33 AM

Quote:

Originally Posted by dugan (Post 4865864)
A lot of Slackers put the following line in /etc/fstab:

Code:

tmpfs            /tmp            tmpfs      defaults        0  0
That mounts /tmp on a RAM drive, so that it's cleared every boot.

actuall, i do

Code:

tmpfs            /tmp            tmpfs      size=4G,mode=777    0  0
ie. limiting the amount of memory and setting permissions

fskmh 05-01-2013 06:46 AM

Quote:

Originally Posted by Martinus2u (Post 4942503)
actuall, i do

Code:

tmpfs            /tmp            tmpfs      size=4G,mode=777    0  0
ie. limiting the amount of memory and setting permissions

+1

Otherwise after a couple of months of uptime you start having issues with things that need to write in /tmp, and then you end up having to use tmpwatch in any case.

ruario 05-01-2013 07:19 AM

Quote:

Originally Posted by Martinus2u (Post 4942503)
limiting the amount of memory

It automatically limits to half the available memory in any case, even if you do not set it


All times are GMT -5. The time now is 10:48 AM.