Re: Linux.pm useradd

[Evelio Quiros <ev...@fiu.edu>]

The "fix" worked for us too.

In our case, it was affecting users who logged into VCL using Shibboleth.
Apparently, the UID was the one from our LDAP.
Local users did not have this problem.

By removing the < -u $user_uid > from the Linux.pm script, the shib user
was able to log into their reservation.

Thanks,
Al Quiros
Florida International University



On 8/29/12 3:39 PM, "Yannick Charbonneau" <yc...@uottawa.ca> wrote:

>Thank you.
>
>We were having that discussion here about adding 500.
>
>Thanks again for the quick reply.
>
>On 2012-08-29, at 3:02 PM, "Dmitri Chebotarov" <dc...@gmu.edu> wrote:
>
>> Hi Yannick  
>> 
>> I have had the same issue with Linux images and did the same - removed
>>-u option from useradd command in Linux.pm.
>> Everything works fine without this option.
>> 
>> I think having the same user id would be important if you need to match
>>userid across multiple Linux system (ie. using NFS mounted volumes,
>>etc.).  
>> But for a single Linux reservation it's OK to let system choose user id.
>> 
>> Another option would be to increment userid by 500 for userid less then
>>500. This is if you need to have the same user id across multiple
>>systems.
>> 
>> Thanks.  
>> 
>> --
>> Dmitri Chebotarov
>> Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
>> 223 Aquia Building, Ffx, MSN: 1B5
>> Phone: (703) 993-6175
>> Fax: (703) 993-3404
>> 
>> 
>> On Wednesday, August 29, 2012 at 14:53 , Yannick Charbonneau wrote:
>> 
>>> Hi All,
>>> 
>>> We encountered an issue with Linux Images, users could NOT connect to
>>>machines.
>>> 
>>> I found in the vcld.log;
>>> 
>>> ³useradd: UID 4 is not unique² my image already had a UID 4.
>>> 
>>> I removed ³-u $user_uid² from $useradd_string and it appears to have
>>>³fixed² the problem.
>>> 
>>> What did I break by doing this? What is the proper way to fix this?
>>>Remove all account except root from the image?
>>> 
>>> Thanks
>>> 
>>> Yanik
>> 
>> 
>>