We're using ldap authentication on our cluster, so our /etc/passwd files don't 
have any user data and the credentials are returned by ldap. You will have to 
adjust this to your situation. You can rsync /etc/passwd from elsewhere or 
fiddle with PAM to work something out for your key-based setup. Sorry, I don't 
have more insight into that part.



On Dec 18, 2012, at 2:27 PM, cgan...@iu.edu wrote:

> Hi Alex,
> I see what you are saying, but I think our situations are slightly different.
> The line 
>                self.__user_system_pwent = 
> pwd.getpwnam(job.user.email.split('@')[0] )
> *does* return the correct username, however, that user is not present in the 
> Virtual machine that is running Galaxy, so when the job runner calls for 
> pwd.getpwuid(), there is nothing there.  By the way, the VM uses key 
> authentication only, not passwords.
> The problem I think I'm having is that the /etc/passwd file I want to use is 
> located on the cluster, not on the virtual machine.  I'm not sure if I can 
> just copy that file over.  How else can I get ahold of the uid of the user 
> who cannot log in to the machine Galaxy is running on?
> Thanks for the help,
> Carrie Ganote

Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:


Reply via email to