sharedfolders mounted with noexec acl issues

  • So I was trying out some new $PATH variables for a users script location but after doing so I was unable to execute scripts?


    Release: 4.1.17-1

    Codename: Arrakis


    Code
    ./x.sh
    bash: ./x.sh: Permission denied


    Code
    bash -x x.sh
    + echo working
    working


    Code
    ls -la x.sh
    -rwxrwx--x+ 1 dave users 28 Apr 1 18:25 x.sh


    I noticed the the drive/sharedfolders in fstab was mount with noexec


    Code
    (rw,noexec,relatime,stripe=256,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)


    so did a


    Code
    mount -o remount,rw,exec /dev/md0


    and it worked again. I've never noticed if it said noexec before today should it be? or what can cause it to change? I even tried a reboot but still the same?

  • I've never noticed if it said noexec before today

    OMV since the beginning has always mounted filesystems noexec.


    what can cause it to change? I even tried a reboot but still the same?

    OMV controls fstab. So, unless you change the database (remove noexec from mntent section in /etc/openmediavault/config.xml), it will keep changing back.

    omv 5.5.1 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • marvelous

    Added the Label OMV 4.x
  • it must be a general ACL issue then? any ideas on what I can check to resolve?

    What is a general ACL issue? noexec that OMV applies has nothing to do with ACLs (I hate them myself). If you want the sharedfolder to have exec privileges, you have to edit the database as I mentioned (and then run omv-salt deploy run fstab).

    omv 5.5.1 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Your users folder must have been on the OS drive (/home) before and you moved it to a data drive? The OS drive is always mounted exec. And why not just remove noexec from the data drive? Then you won't have to worry about it.

    omv 5.5.1 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.3.3
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!