Which files and directories can I delete?

After custombuild runs, which files and directories can I delete? This is what I noticed. After my MySQL upgrade, I have the old MySQL tarball, and it looks like a tarball of the data in /usr/local. In the custom build directory, I have a source tarball of the old MySQL. In the directories in there, I have an httpd-2.2.15 directory, but I'm not even on it. I'm on 2.4, and I don't have a 2.4 directory. I don't understand this area of DA very well.

The reason I'm asking, is I need to clean house because when I tried to retrograde to Apache 2.2, I ran out of disk space, so I reverted to the snapshot, which put me back on 2.4. The problem with 2.4 is it is not ready, and is causing app issues for me.

Thanks!

Hello,

What if you run


will it help you?

zEitEr said:

What if you run

Code:

./build clean

will it help you?

Click to expand...

I did that first. It didn't change a thing, probably because I have that set in my options.conf.

Thanks!

In the options.conf I have:
clean=yes
clean_old_tarballs=yes
clean_old_webapps=yes

That doesn't do it. If there are good reasons for what I see, I'm OK with that. There are just some things that don't make sense, so I don't know if it's a script problem or what. If the MySQL issue is a safety thing, and that I'm supposed to delete it later, I'm OK with that. And I didn't ask for a backup BTW. The httpd thing makes no sense when I install Apache 2.4, and end up with 2.2.15 and 2.4 source, and it finishes running 2.4 with a 2.2.15 directory in custombuild, and no 2.4 directory. And with everything set to clean, this isn't what I naturally expect, so I decided I need to understand this area a little better so I know what I'm supposed to/can clean up manually, and what I'm not.

Thanks!

You can delete the backups once you're sure that everything mysql related is working as it should be. Note I don't guarantee anything because I'm not looking into your server, but this should be okay.

Jeff