[prev in list] [next in list] [prev in thread] [next in thread] 

List:       npaci-rocks-discussion
Subject:    [Rocks-Discuss] Re: Rocks BUG setting up a user account ?!
From:       Christophe Guilbert <cguilbert () picasso ! ucsf ! edu>
Date:       2018-02-08 1:12:16
Message-ID: 8fcfe80a-30cb-a46f-af60-6c4bdf396b80 () picasso ! ucsf ! edu
[Download RAW message or body]

Thanks
I did not do any particular step , my user account should have been 
created during the installation.
I checked /etc/group and /etc/passwd and it is not what I expected. I 
used the advance setting to create a user account , in the advance tab, 
you can choose the UID and GID but for some reason there has been a 
mixed up and the install did not create my home folder , I did not get 
any warning for that . I'll will correct that . Thanks

On 02/07/2018 05:01 PM, Evgenii wrote:
> Chris,
> 
> Are you doing all the necessary steps?
> 
> 
> - /usr/sbin/useradd -u UID USERNAME creates the home directory in
> /export/home/USERNAME (based on the settings in /etc/default/useradd) with
> UID as the user ID. If the desired user ID or the group ID has already been
> used, change them using:
> 
> 
> - rocks sync users adjusts all home directories that are listed as
> /export/home as follows:
> 
> 
> 1. edit /etc/password, replacing /export/home/ with /home/
> 2. add a line to /etc/auto.home pointing to the existing directory in
> /export/home
> 3. 411 is updated, to propagate the changes in /etc/passwd and
> /etc/auto.home
> 
> 
> 
> On Wed, Feb 7, 2018 at 6:47 PM, Christophe Guilbert <
> cguilbert@picasso.ucsf.edu> wrote:
> 
> > Yes , I used Rocks 10 years ago, my memory comes back now.
> > but the problem (bug ?) remains.
> > my /etc/auto.home file is empty .
> > /etc/auto.home should have something  like that:
> > chris   jcluster.local:/export/home/chris
> > 
> > For some reason the install did not created chris in /export/home/chris
> > 
> > 
> > On 02/07/2018 04:18 PM, Evgenii wrote:
> > 
> > > just to quote:
> > > 
> > > "In the default Rocks configuration, /home/ is an automount directory. By
> > > default, directories in an automount directory are not present until an
> > > attempt is made to access them, at which point they are (usually NFS)
> > > mounted. This means you CANNOT create a directory in /home/ manually! The
> > > contents of /home/ are under autofs control. To "see" the directory, it's
> > > not enough to do a ls /home as that only accesses the /home directory
> > > itself, not its contents. To see the contents, you must ls
> > > /home/username."
> > > 
> > > On Wed, Feb 7, 2018 at 6:14 PM, Christophe Guilbert <
> > > cguilbert@picasso.ucsf.edu> wrote:
> > > 
> > > Hi ,
> > > > I met this "Bug" in a real computer and in a VM .
> > > > 
> > > > When creating the  user chris  with a specific user and group ID. The
> > > > /home/chris folder was not created.
> > > > 
> > > > As root, I tried to created the missing folder by hand using mkdir
> > > > /home/chris . I had the following message:
> > > > 
> > > > mkdir chris
> > > > mkdir: cannot create directory ‘chris': Permission denied
> > > > 
> > > > Any explanation ?
> > > > 
> > > > Thanks
> > > > 
> > > > 
> > > > -------------- next part --------------
> > > An HTML attachment was scrubbed...
> > > URL: http://lists.sdsc.edu/pipermail/npaci-rocks-discussion/
> > > attachments/20180207/a572df4b/attachment.html
> > > 
> > 
> > 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20180207/51301207/attachment.html
> 


[prev in list] [next in list] [prev in thread] [next in thread]