Sorry, I missed your post.


Ok so no package installed. But this app runs. So I guess certain apps can be "installed" and run without being an actual package?

What I need is to find all the files this intall has has placed on the machine, is there a easy way to search for a specific file name?

And thank you for all the replies. :)

Yes, you can run it, installing it puts it in a specific place you see so you don't have to navigate to the directory it is in. It also sets configuration files in certain places and so on, and so forth.

EDIT: Consider it as in Windows. You can run a standalone program easily. You can write a program easily. Installing it puts the program in a specific directory and adds it to the registry. It does the Linux equivalents here. You didn't install, you just ran it.

At the terminal type in
These directories are where executables are saved to/moved to to enable you to just type in 'command' instead of doing the 'cd /command/path; ./command' dance you had to do.

But yes, type in
to find it. Still, all you need to do is really delete than directory and its gone. Is there something thats making you think splunk has put something on there? Outside of this directory?

Well I'm not exactly sure how splunk works on this machine. I wanted to un/re install it because it won't work anymore. It runs like a local web page type of thing and it can't start a service called 'splunkd' so I was assuming it installed this on the machine. I may just blow away this virtual machine and start fresh.

Personally, I'd make sure it wasn't running
- If it was killing each instance

Then delete the directory, then install the package with yum. Easier than binning the whole thing.

Since the http://www.splunk.com/download URL contains a splunk RPM, I'd simply delete the directory where you installed it (presumably from the .tgz file rather than the rpm package available on their website) download the rpm and install with: -

rpm -ivh splunk-4.0.9-74233.i386.rpm

Job done. You don't need to worry about where it installs it, as the package will sort that out for you. And it's easily uninstalled if you so choose with: -

rpm -e splunk-4.0.9-74233

..or with whatever the output from "rpm -qi splunk" returns.

Indeedy :D

Although splunk isn't available from Fedora's repos, as I've just checked...hence my recommendation to install via the rpm package available on their website.

awesome thank you!

is there a way to be ROOT when I am trying to delete files or whatnot when using the GUI? Or must I be in Terminal?

You can launch the GUI application from a root terminal.

Since, from your bash_history, you seem to have installed splunk to: - /home/kryznic/Downloads/opt/splunk/bin, you can run: -

cd ~/Downloads
rm -rf opt

...assuming that 'opt' has nothing else but splunk in it, else cd ~/Downloads/opt and do the rm thing again.

CAUTION: Make sure you're in the right directory when you do this (run 'pwd' to find out where you are) - it will not prompt you for deleting files, nor will you be able to retrieve them from the GNOME trash can if you do this, that directory and everything below it will be gone for good.

here's what I am attempting to do. I searched in the File Browser for files containing the word "splunk" I found many and want to delete them all but keeps telling me access denied. How can I gain access thru file browser?

Thanks fella's

From the looks of it, all splunk files should be in the directory you specified, which I mentioned above. I highly caution you about deleting files randomly from all parts of the filesystem - you'll most likely cause your system to become unstable at best and non-functional at worst. WHat makes you think that splunk files have been installed all over your filesystem?

As mentioned above, you should be able to run the GNOME nautilus file manager from root by simply running "nautilus" from your root account, although personally I've never tried this.

This, and the fact that I still see files in other folders that are not located in the 'opt' folder.

[root@FedoraBox kryznic]# rpm -ivh splunk-4.0.9-74233.i386.rpm
warning: splunk-4.0.9-74233.i386.rpm: Header V3 DSA signature: NOKEY, key ID 653fb112
Preparing... ########################################### [100%]
package splunk-4.0.9-74233.i386 is already installed
[root@FedoraBox kryznic]#


I officially give up though, I am going to reinstall Fedora and start fresh. Thanks for all the help ;)

well I dunno why, but I went into users and groups and found a splunk user, I deleted it and then ran rpm -ivh splunk-4.0.9-74233.i386.rpm and it re-installed splunk and now it works. That makes no sense to me.

Also, does rpm -ivh splunk-4.0.9-74233.i386.rpm actually install the package so that it could be removed through my package installer? I am still confused on how this works.

Thanks.

Well, perhaps part of the check that RPM does to signify if splunk is installed is checking for the user for that application - since it was there, the new install failed, as it assumed correctly that splunk was already installed via another means.

As for packages, dude - you really need to read up on this stuff. It's not that hard. "man rpm" and "man yum" would be a good start and as they say, "Google is your friend" :) Anyhow - RPM -ivh is: -

i = install
v = verbose mode
h = show hash marks install progress

And yes, installing an RPM file via RPM adds this entry to the RPM database and because of this, allows you to uninstall it cleanly.

YUM is sorta a wrapper on top of RPM - it queries remote repositories of validated applications and installs them much like RPM files. One of the problems with RPM packages is that that RPM file might have dependencies that depend on other RPM packages, which you have to download manually and install first, the so-called "dependency hell". Yum handles this for you by downloading and installing any dependant packages from the remote repositories as well so you don't have to do it yourself. Always try "yum install <package name>" first. If it's not available in any of your remote repositories, them hunt down an RPM package file from the net and try that (and possibly any dependant RPM package files it needs). Lastly install from source using zipped source files. This usually allows various switches to the configure script to denote installation destination and various other things. You can then use make and make install to actually install the application. But this means you'll have to uninstall the application manaually, so make a note of where you installed it.
That's vaguely it anyways.

All this stuff can be researched on the net. Good luck.

Arashi, thank you. Your right I do have to read up and I will be doing so. I just had a little panic attack here and I was getting frustrated working on this for the past few days. Thanks for everyone's help and patience. I leave this thread having gained some valuable linux info. :)