Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 1
    A little more context might be helpful. I'm unclear why you need custom permissions. Can you elaborate? Commented Feb 24, 2016 at 20:14
  • Root owns the folder, but the program is run by standard user. When the program attempts to write on the folder, it fails due to lack of permissions. Commented Feb 25, 2016 at 8:48
  • Well, ok, but why is it set up this way, and do you have the ability to change it? Needless to say, this isn't a standard setup. One way to go is to create a system user/group for that program. There are many such on your system. You can see them in /etc/group. Regular owners do not normally own system files. Commented Feb 25, 2016 at 10:03
  • 1
    Note that if you are installing using a deb, then you should not install in /usr/local. That would be a violation of the FHS and Debian policy, and generally a bad idea. I recommend using a proper build system. Both autotools and cmake are popular. A handwritten makefile or similar is also an option, but would require more manual work. Commented Feb 25, 2016 at 11:21
  • 2
    Debs are by definition not locally installed. Commented Feb 25, 2016 at 14:22