Where does the client store files?

I am running SL on a 2005 dell, RHEL3. I have it running out of a folder inside my home directory. I have a limited amount of space, 200MB quota altogether. When I tried running it today, it was wonderful, smoother than any other computer I've tried SL on, mainly because it is so much newer and it connected to a much faster network.

But it eats up my disk quota really fast, and once I run out of space the app freezes on me. So I need to mess with the cache settings to keep this from happening. Before downloaded the client, I had 64 Megs of my 200 meg quota full. I ran SL for a couple minutes and it ate all my quota then froze my system. I removed both the tar file and the entire extracted SL directory, but now my quota says I am still taking up 109 MB or space. i should be down to 64 again after removing all the SL stuff I downloaded, that was the only thing that changed.

The only reasonable explanation is that SL has stored some stuff in my user space which I have not deleted yet, and I need to find this stuff so I can make enough room to fit SL so that I can try running it again, this time configured to use the disk space more sparingly.

Can somebody tell me all of the places the linux SL client takes up my disk space so I can find and clear it to make room in my quota?

nevermind, I found a folder where all my deleted stuff was going, and I purged it, now I'm back to normal quota and can try again, yay

Just to add, as the cache files are wiped everytime you restart the Linux client there is little advantage in having a huge cache file.

I still need to trim down the disk spce this thing uses, I already deleted the help folder.

I was considering gettig rid of the library files, since they are also avaiable on the system outside of my home directory. I wonder if just deleting them would cause the client to look for thse same folders at the standard library locations? or should I make symlinks to those files?
There is also that 50 meg secondlife script that I am tepted to try and remove or trim down.

Basicially I want to run SL with it using up as little of my disk quota as possible, how can I trim the size down?

You can safely remove (most) of the libraries. The standard Linux method for finding libraries is used (basically, the local lib directory is added to the LD_LIBRARY_PATH, at the beginning). A few libraries are required because of their versions, I *think*... move them to a backup location and try the game, see which ones it complains about

Just to make sure: you turned down the SL cache to the lowest possible setting, didn't you?

I did that, another problem I notice is that I cannot upload files nor export them from SL to my linux box.

The Linux client is still not working completely. The most important things that are missing are Cut & Paste, Hotkey support and File upload. If you want to make textures, sounds or animations you will have to use the windows version of the client in WINE / cedega for now or find someone, who can upload them for you.

And sound! Sound is also missing.

And worst of all, for Texture rezzing, the client does not detect system memory, and there is no override to tell it explicitly how much you have.

Correction: it does not detect ALL of system memory. It detects 1 MB

Further correction: it reports the number of Gb you have as Mb. Your system detects 1 Mb because you have 1 Gb system memory. My fiancee's machine shows 0 Mb, she has 384 Mb memory. I've checked this on several machines, and that seems to be correct.

Which means it's probably a one-line code fix.

Doesnt help me that it is dividing by 1024

In the texture console it ACTS as if I have 1 MB, indicating that all my texture cache is full. It sees my graphics ram OK as per settings.ini, according to this, but effectively, SL Linux knows I have 1 MB of memory ...

I am sure LL will find that line sometime...

Could be that the linux version is a port of the windows version, and windows reports memory detected in bytes, linux in kilobytes... If that is the case, LL should not find it that hard to find the "one liner"

And that was actually a VERY astute observation: memory IS being detected! I would never have spotted that