Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I had to do a bunch of things to get Drush working on my shared host and it seems to be working, except I get the following error every time I run it:
/home/XXXX/drush/drush: line 26: /bin/uname: Permission denied
If I had to guess, it must have something to do with the jailedshell permissions. Is this anything I need to worry about?
Comment | File | Size | Author |
---|---|---|---|
#4 | drush-1784174.patch | 613 bytes | jonhattan |
Comments
Comment #1
greg.1.anderson CreditAttribution: greg.1.anderson commentedDrush is only calling uname to see if you are running on Cygwin, which you are not. As a workaround to this problem, you could make sure that $HOME/bin occurs in your PATH before uname does, and make your own uname script that does nothing.
e.g.: in $HOME/bin/uname
Don't forget to chmod +x your uname script.
Comment #2
modctek CreditAttribution: modctek commentedWorked like a charm, thanks!
Comment #4
jonhattanI'm also experiencing this in a shared hosting with chrooted ssh access. I think this is a increasingly common scenario.
The warning can be avoid easily if we check the user has rights to execute uname.
Comment #5
greg.1.anderson CreditAttribution: greg.1.anderson commentedI don't have a restricted shared host environment to test #4 on, but it works fine on normal environments, and looks like a good thing to do in general.
Comment #6
greg.1.anderson CreditAttribution: greg.1.anderson commentedChanging classification to feature request - support restricted environments with no access to uname.
Comment #7
jonhattanCommitted to both branches.