95

So I've been trying to copy images in an existing, writable directory. Here is a Patrick meme I created to avoid getting insane.

Comments
  • 3
    You have double-checked ownership? Your user could be "hated" even though permissions are 777

    Chown ;)
  • 1
    I know this.
    If you for example:
    - add yourself to a specific group
    - allow that group to write to a directory
    - restart your shell/terminal

    and you still can't write to it.

    You can in this case either:
    - Restart your computer (logout + login may work too)
    - Run "$ su -" (gives you a session where it should work)

    -----

    Also a nifty trick:
    Use "# chown g+s DIRECTORY -R" to not change the group when creating files/folders.
    Especially handy when you copy files as root into a directory and cant delete these files with you regular user/group.
  • 2
    Check acl too, basic permissions are basic
  • 2
    Might be worth looking up its SELinux label providing its a RHEL based OS. "ls -Z"
  • 0
    @andros705 nah, it's a random directory created on the fly, with chmod 775 by default which is more than fine to begin with, and all of that inside a Laravel project

    While Laravel, with such configuration, can write without trouble in this directory, Intervention Image, an external library, CAN'T. WHY.
  • 1
    Ever heard of SELinux you absolute muppet?

    I bet you've either forgotten to (re)label your file contexts or are writing to a segregated temporary directory (i.e. your /tmp isn't actually in /tmp.)
Add Comment