@ub & @cb issues

[Bill Vermillion]

On Tue, Apr 20, 2004 at 04:01:06PM -0400, Tim Fischer thus spoke:
> Bill,

> You lost me there. What do you mean "change their UID to the
> missing one"? What's the missing one?

When you see a number in the CB or UB field that is the UID of the
original creator/updater.  The programs grabs that UID and goes to
the password file to get the matching UID [User ID number] and then
print the name.   If there is no matching UID it displays the
number.

> We did find something though - The old UIDs (SCO) were 4 digits
> while the new UIDs (Solaris) are 5 digits. Would that make any
> difference?

That should make no difference.  A few years back Solaris expanded
the UID field capability to be 10 digits.  [It may have been only
9].  That was so that students in large University environments
could have the UID match their SSN.  That was before all the
concern over purloined SSN numbers.

Most systems will let you change the IDs.  When you do that and
file created by the person with the current ID will now show
ownership of just the ID number and not the person's name.

In that case you correct that by going to the top of the tree
when any files they may have reside and used the 'find' program
with the -user flag and the ID as the 'name' of the user.

Then you perform a chown own those.

find . -user 545 -exec chown <username:usergroup> {} \;

That is one way to do it.  You can use xargs also.


> -Tim
> 
> > -----Original Message-----
> > From: filepro-list-bounces at lists.celestial.com 
> > [mailto:filepro-list-bounces at lists.celestial.com] On Behalf 
> > Of Bill Vermillion
> > Sent: Tuesday, April 20, 2004 3:50 PM
> > To: filePro Mailing List
> > Subject: Re: @ub & @cb issues
> > 
> > On Tue, Apr 20, 2004 at 03:33:56PM -0400, Tim Fischer thus spoke:
> > 
> > > The database was moved, however the only users we're seeing 
> > the issue 
> > > with are newly created (on the new server). All old users work fine 
> > > and, just to make things even more weird, some new users work fine.
> > 
> > Then find the user with the problem and change their UID to 
> > the missing one.  However, anyting they created up to now 
> > will start showing the current UID.  In that case you can 
> > make a user with the old UID, and you could make it with no 
> > password, and give it
> > a name.   If it were your login [as an example] you could make an
> > ID called 'oldtim'
> > 
> > Setting up new machines and migrating data means you have to 
> > sychronize the password file to have the same UID/GID, and 
> > different OSes start with lower default UID's than others.
> > 
> > Bill
> > --
> > Bill Vermillion - bv @ wjv . com
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
> > 
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 

-- 
Bill Vermillion - bv @ wjv . com