Re: Program runs for "root", not for regular user
From: Robert Oschler (no_replies_at_fake_email_address.invalid)
Date: Tue, 15 Jun 2004 15:35:25 -0400
<email@example.com> wrote in message news:firstname.lastname@example.org...
> Robert Oschler <no_replies@fake_email_address.invalid> wrote:
> drwxr-x-r-x is correct for him directories...
> first triplet == user
> second == group
> third == all
> so unless you want everyone in your group (users) to have access to your
> home directory, or everyone in the world (if you set write on the last
> triplet), it's best to leave it as it is.
> A lock file is generally used to prevent the user from opening more than
> one instance of an application that would otherwise interfere with itself.
> In a multiuser system, more than one user should be able to use it,
> the app's files are stored in the individual home of each user, so no
> cross user interference will occur.
> Try starting it as both your normal user and root (or another test user
> created for the purpose).
I'm a bit baffled at the moment. You're right, the /home/me-the-user
directory was indeed set to be owned by "users", although not "me-the-user".
However, setting the permissions to "a+w" did solve the problem (yes I am
aware that this opens up my home directory to other users).
/home is indeed set to ownership by root with permissions of drwxr-xr-x
komodo, the binary, has permissions: -rwxrwxr-x with root as the owner, and
is located in /usr/local/Komodo-2.5 which has permissions drwxr-xr-x with
root as the owner.
However, without the permissions set to "full write" in /home/me-the-user, I
get a permissions error when komodo tries to write the lock file.