[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Permission Denied



Jennifer Waters wrote:

Here are the answers to the three commands:

1. ll / |grep home
  drwx------  1361 root root 28672 Oct 11 11:06 home
2. ll /home | grep jwaters
  drwxr-xr-x  7 jjwaters jjwaters 4096 May 27 18:06
    jjwaters
  drwxr-xr-x 44 jwaters jwaters 4096 Oct 11 10:33
    jwaters
3. id jwaters
  uid=501(jwaters) gid=501(jwaters) groups=501
    (jwaters)

Thank you for your help

Jennifer



Your mode on /home is a problem, and would cause your problem symptoms. Usually it looks like this:
drwxr-xr-x 12 root root 4096 Oct 5 09:11 home
So as root you can enter this command to fix that, then test your user login again:
chmod go+rx /home
Which will add read and execute permission to /home for the group root (not all that important), and for other (all users). The read permission is necessary to see what is in the directory, and the execute permission is necessary to actually locate the inodes to get at the files or directories in /home. So without those permissions user jwaters could not get at /home/jwaters to make it the current directory, nor to read files under there during initialization of the login shell.


BTW unless you actually do have need for a jjwaters account in addition to jwaters account, that may be a relic of an earlier name to userid assignment scheme. If so you need to do some cleaning out of accounts and their home directories at a more opportune time. Old accounts mean old passwords that still have system access. And may mean that there are files there the user (under new account) has been looking for.

--
-----------------------------------------------------------
  "Spend less!  Do more!  Go Open Source..." -- Dirigo.net
  Chris Johnson, RHCE #807000448202021





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]