Ok so which files did you change permissions for, and to what? Has anyone got this to work with 7.1? I've tried everything and nothing has worked thus far.

lw needs to run with root-authorisation. Someone mentiones to change the whole path where LW is installed (/opt/LimeWire ... ?) to SUID root. ( see man chown).

I solved it using sudo...There's more than one way to do it

First, what distribution do you mean with linux 7.1? As far as I know there are at least RedHat Mandrake and SuSE with an 7.1!
And then, because of security reasons I would never dare to launch a filesharing software with root permissions and I don't think you have to do that.
As for me on a Debian system, I've installed LimeWire as a normal user under my home directory and to start it I simply use 'sh LimeWire &'; no dealing with permissions, and it works for me.
Eventually, if you've installed it as root, you could try to make the user the owner of the LimeWire subdirectory and its files. E.g. if you have installed it in /opt/LimeWire and the user Joe in group audio should use it, do something like 'chown -Rc Joe.audio /opt/LimeWire'.

Well, I tried several, but everything failed as long as i didnt start it with sudo root.

One option might be that every user installs it locally...but there are probably better ways to waste space :-|

Anyway, I'll give it a try on the group authorisations, and post the result.
(BTW: I'm on a SUSE 6.3 system)

I've figured it out, thanks. I am using Red Hat. Anyway, I couldn't get it to work by changing any of the authorizations, and I even gave my regular user ownership of the files, still to no avail. I'm not sure why, but I just created a new directory in my home directory and changed that directory to my download/upload folder, and it will now work. I have to change it to the default folder every time I restart limewire, as it doesn't seem to remember my configuration, but at least it works!

@ Axe:

You really have several users on a single machine doing LimeWire? I hadn't thought that this could be useful.
But yes, then every user should have his own configuration files. At least you need a dedicated port for every user to avoid conflicts. And I think the startscript (LimeWire) is looking for files in its own directory.
As for the program itself (LimeWireLinux.bin and the jre subdirectory) I would try to make a 'ln -s' to save space. I don't think you need to be owner or have write-access to that.

Hi GreyFool,

of course not all at the same time ;-| but several have access.

At least I tried changing the ownership to group users...and it still didnt work (no connect), whereas the sudo-solution works fine @:-|

Cheers
Axe

Ok, I've done some Tests and here is how my /home/user/test directory looks like:

drwxr-sr-x Incomplete
-rw-rw-r-- LimeWire
lrwxrwxrwx LimeWire.jar -> /opt/LimeWire/LimeWire.jar
lrwxrwxrwx LimeWire.lax -> /opt/LimeWire/LimeWire.lax
drwxr-sr-x Shared
lrwxrwxrwx collections.jar -> /opt/LimeWire/collections.jar
-rw-r--r-- gnutella.net
lrwxrwxrwx jre -> /opt/LimeWire/jre/
lrwxrwxrwx lax.jar -> /opt/LimeWire/lax.jar
-rw-rw-r-- limewire.props
lrwxrwxrwx swing.jar -> /opt/LimeWire/swing.jar

/opt/LimeWire and subdirectories are owned by root and it runs without any changes to permissions.
Remember that the startscript 'LimeWire' has to be in the directory directly,
doing a 'ln -s /opt/LimeWire/LimeWire . ' doesn't work.