[SOLVED] What to do with /tmp after all Slackbuilds are built and functioning?

mralk3 · 05-28-2015, 06:18 AM

Is it customary to delete /tmp files as described here after desired Slackbuilds are installed? Or should I just leave /tmp alone? Will clearing /tmp affect sbopkg functionality?

I am accustomed to Debian clearing /tmp automagically each reboot. Temp directory is taking up quite a bit of space on my root partition.

Code:

~# du -h --summarize /tmp
4.5G	/tmp

Didier Spaier · 05-28-2015, 06:27 AM

Quote:

Originally Posted by mralk3

I Will clearing /tmp affect sbopkg functionality?

Not at all. If you rm -r /tmp/SBo it will be recreated next time you use sbopkg. Or just empty it.

Needless to say, you can archive the packages you just built somewhere.

PS I am impressed how fast you got acquainted with Slackware

lems · 05-28-2015, 07:15 AM

To clear /tmp at every reboot, put this into /etc/rc.d/rc.local_shutdown:

Code:

#! /bin/sh

echo Cleaning /tmp ...
/usr/bin/find /tmp -mindepth 1 -maxdepth 1 -exec /bin/rm -rf {} +;

and make it executable.

edit: For more information, see this article on the wiki:
http://docs.slackware.com/howtos:gen...ree_your_space

GazL · 05-28-2015, 07:27 AM

I do things manually rather than use 'sbopkg' as I generally want to meddle with the slackbuild in one way or another before running it. I keep both the build directory (in case I ever need to rebuild) and the resultant packages (in case I need to reinstall). Anything left over in /tmp after a build gets cleared out.

Here's an example.

Code:

$ tree .
.
|-- builds
|   |-- libasr
|   |   |-- README
|   |   |-- libasr-1.0.1.tar.gz
|   |   |-- libasr.SlackBuild
|   |   |-- libasr.info
|   |   `-- slack-desc
|   `-- opensmtpd
|       |-- README
|       |-- aliases
|       |-- doinst.sh
|       |-- libasr -> ../libasr
|       |-- opensmtpd-5.4.5p2.tar.gz
|       |-- opensmtpd.SlackBuild
|       |-- opensmtpd.info
|       |-- rc.smtpd
|       `-- slack-desc
`-- packages
    |-- libasr-1.0.1-x86_64-1_local14.1.tgz
    `-- opensmtpd-5.4.5p2-x86_64-2_local14.1.tgz

5 directories, 15 files

The symlink (highlighted blue) I create to remind myself of any needed dependencies and to aid navigation.

Your approach to this sort of thing will evolve over time as you find what works best for you. This is just what works for me.

mralk3 · 05-28-2015, 07:53 AM

Quote:

Originally Posted by Didier Spaier

Not at all. If you rm -r /tmp/SBo it will be recreated next time you use sbopkg. Or just empty it.

Good to know.

Quote:

PS I am impressed how fast you got acquainted with Slackware

Thanks! I have been using Slackware either in a virtual machine or as a hard drive installation for ~3 weeks. The documentation on docs.slackware.com is excellent. The tutorial style format is very helpful in explaining the Slackware way. Once you understand the Slackware philosophy, things just click. I've even started building my own Slackbuilds and storing them on my github account.

mralk3 · 05-28-2015, 08:00 AM

Quote:

Originally Posted by GazL

I do things manually rather than use 'sbopkg' as I generally want to meddle with the slackbuild in one way or another before running it. I keep both the build directory (in case I ever need to rebuild) and the resultant packages (in case I need to reinstall). Anything left over in /tmp after a build gets cleared out.

(..snip..)

Your approach to this sort of thing will evolve over time as you find what works best for you. This is just what works for me.

I was doing something similar to this before I learned of the instant gratification of sbopkg.

According to the sbopkg.conf man page, it's possible to switch where sbopkg stores it's /tmp and build directories. I will have to mess with that and see if it satisfies my needs.

Though I might start building all my slackbuilds manually again and write a ruby script that queries/scrapes slackbuilds.org and downloads the appropriate files for each Slackbuild. The main thing I like about sbopkg is how it locates each slackbuild and uses the queue files to grab the dependencies too.

ponce · 05-28-2015, 08:35 AM

Quote:

Originally Posted by mralk3

According to the sbopkg.conf man page, it's possible to switch where sbopkg stores it's /tmp and build directories. I will have to mess with that and see if it satisfies my needs..

to erase build files at the end of the build queue everytime I launch sbopkg here I have this variable set in /etc/sbopkg/sbopkg.conf

Code:

CLEANUP=${CLEANUP:-YES}

1337_powerslacker · 05-28-2015, 09:10 AM

Additionally, if you have the RAM to spare, you can mount your SBo directory as a RAMdisk, and then it will clear every time you reboot/shutdown. Quoting from slackalaxy's website:

Code:

I like to speed up the compiling process by compiling in RAM. Almost all additional software that I use is installed from SlackBuilds.org. Scripts from there use /tmp/SBo for compiling, as can be seen from the templates files.

So, I made sure that /tmp/SBo exists and is empty. Then, I just added the following row in my /etc/fstab file:
11
12
13
14
	
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
tmpfs            /dev/shm         tmpfs       defaults         0   0
SBo              /tmp/SBo         tmpfs   nodev,nosuid,size=7G 0   0

Reboot. I have 8GB of RAM, so I set 7GB for the size.

I got the idea from the time I used CRUX and reading their wiki. Another way is to just mount the whole /tmp folder in RAM.

Happy Slacking!

dugan · 05-28-2015, 09:22 AM

The first thing I do when installing Slackware is put the following in fstab:

Code:

tmpfs /tmp tmpfs defaults 0 0

bassmadrigal · 05-28-2015, 09:54 AM

Quote:

Originally Posted by dugan

The first thing I do when installing Slackware is put the following in fstab:

Code:

tmpfs /tmp tmpfs defaults 0 0

Does that just expand in size as needed? What if you start getting low on memory? If you remove stuff in /tmp, does it give that space back to the system for memory use?

I ask because I've been wanting to do this for a while, but I'm constantly using a good chunk of my 8GB (stupid Chrome), which is the the max of my motherboard, and I'm worried I'd run out of space on either /tmp or my RAM considering I usually have uptimes of at least several months. Once I build a new computer with more RAM, I'll definitely be doing this.

lems · 05-28-2015, 11:24 AM

Quote:

Originally Posted by mralk3

Though I might start building all my slackbuilds manually again and write a ruby script that queries/scrapes slackbuilds.org and downloads the appropriate files for each Slackbuild. The main thing I like about sbopkg is how it locates each slackbuild and uses the queue files to grab the dependencies too.

No need to scrape the website, since 13.1 there is a file called SLACKBUILDS.TXT that you can use to get information about a package; since some time it also carries the REQUIRES information. Then it's easy to download the SlackBuilds tarball if you got the subdirectory and name of the SlackBuilds (like audio/mpd -> .../audio/mpd.tar.gz). (Personally, I started with a small script that would just download the SlackBuilds tarball with its dependencies and all required sources, but it evolved into something a little bit bigger now.)

neymac · 05-28-2015, 11:33 AM

Quote:

Originally Posted by lems

To clear /tmp at every reboot, put this into /etc/rc.d/rc.local_shutdown:

Code:

#! /bin/sh

echo Cleaning /tmp ...
/usr/bin/find /tmp -mindepth 1 -maxdepth 1 -exec /bin/rm -rf {} +;

and make it executable.

edit: For more information, see this article on the wiki:
http://docs.slackware.com/howtos:gen...ree_your_space

As my ~/.xsession-errors grows to much I added to /etc/rc.d/rc.local_shutdown:

Code:

#Change ~/.xsession-errors to 100 lines if greateer than 1 mb
if [ $(du -b ~/.xsession-errors | cut -f1) -gt 1048576 ]; then
  KEEP_LINES="$(tail -n 100 ~/.xsession-errors)"
  echo "$KEEP_LINES" > ~/.xsession-errors
fi

to reduce its size.

dugan · 05-28-2015, 11:35 AM

Quote:

Originally Posted by bassmadrigal

Does that just expand in size as needed? What if you start getting low on memory? If you remove stuff in /tmp, does it give that space back to the system for memory use?

I don't know the answers to any of these, but I do it on a machine with a 32-bit installation and 4GB of RAM and I've never had problems.

It's a laptop that gets turned on and off as needed though.

Gerard Lally · 05-28-2015, 11:44 AM

Quote:

Originally Posted by bassmadrigal

Does that just expand in size as needed? What if you start getting low on memory? If you remove stuff in /tmp, does it give that space back to the system for memory use?

I ask because I've been wanting to do this for a while, but I'm constantly using a good chunk of my 8GB (stupid Chrome), which is the the max of my motherboard, and I'm worried I'd run out of space on either /tmp or my RAM considering I usually have uptimes of at least several months. Once I build a new computer with more RAM, I'll definitely be doing this.

You can limit /tmp to a percentage of your RAM:

Code:

tmp /tmp tmpfs defaults,nosuid,size=50%,mode=1777 0 0

solarfields · 05-28-2015, 12:37 PM

mattallmill,

i am flattered you are quoting my humble blog, but please remove the line numbers, because they got messed when you pasted the text. Here's the post if someone is interested:

https://slackalaxy.wordpress.com/201...piling-in-ram/