• [6.9.0] /etc/profile.d changes are breaking ability to spawn shells in certain directories

    • Minor

    Attempting to start bash shells in specific directories under tmux fails.

    Upon investigating it seems these lines in /etc/profile have cause all login shells to forcibly open in /root

    # limetech - modified for unRAID 'no users' environment
    export HOME=/root
    cd $HOME


    This didn't occur in the last stable version 6.8.3 or earlier.


    Workaround is to edit the /etc/profile to remove the offending lines.


    I don't understand the rationale behind this.

    User Feedback

    Recommended Comments


    I don't understand the rationale behind this.


    I don't remember why either ;)   What breaks when you revert that change?

    Link to comment
    18 hours ago, ken-ji said:

    Nothing that I have noticed. So it should be safe to revert in the next version. 😛


    Realize Unraid OS is designed as an appliance, not a general purpose multi-user server.  Creating users with login shells and home dirs, etc., is not supported.

    Link to comment

    I'm simply running multiple root shells under tmux with each shell in its own directory. I think that's a fair use of unraid, without going into the whole other users can of worms.


    So you can imagine my surprise when a simple login shell refused to open in the specific directory I had it open.



    • Haha 1
    Link to comment

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

  • Status Definitions


    Open = Under consideration.


    Solved = The issue has been resolved.


    Solved version = The issue has been resolved in the indicated release version.


    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.


    Retest = Please retest in latest release.

    Priority Definitions


    Minor = Something not working correctly.


    Urgent = Server crash, data loss, or other showstopper.


    Annoyance = Doesn't affect functionality but should be fixed.


    Other = Announcement or other non-issue.