[p4] preventing use of same client on 2 different computers

[Eric Scouten]

Agreed. I wouldn't want it either. We use the same hostname -> client name 
convention that Rick just described.

It's a one-time thing; walk your users through it correctly when they first 
set up, and life is good from then on.


At 10/20/1999 13:41, Rick Macdonald wrote:
>On Wed, 20 Oct 1999, Glenn Kasten wrote:
>
> > We've just converted to Perforce, and some of our new users are making
> > the mistake of trying to use the same client on different computers.
> > Unless the root directory is a share or NFS mount, this will confuse
> > the p4 server.
> >
> > I would like to suggest that a new field be added to the client form,
> > which is the computer name. By default it would be the name of the
> > computer the client was created on. Users could change it to be a list
> > of computers, or any computer if they know it is safe. This would
> > prevent users from accidentally using a client on the wrong machine.
>
>...by default it should allow any host, as it does now!
>
>I wouldn't want this. We simply put the hostname in the client name.
>
>I find it handy to switch to various clients and see what they're sync'd
>to, run preview syncs to see what is out-of-date, etc, from any machine or
>even from home while dialed up to the office.
>
>...RickM...
>
>
>_______________________________________________
>perforce-user mailing list  -  perforce-user at perforce.com
>http://maillist.perforce.com/mailman/listinfo/perforce-user

__________________________________________________________________________
Eric Scouten <eric at scouten.com>          Software engineer @ Adobe Systems
THIS MONTH on www.scouten.com (Aug '99):    Landscape & nature photography

       * Lightning! (2 slides)
       * Garden tour (29 slides)
       * Four desktop images
__________________________________________________________________________

I find myself up my stream of consciousness without a paddle.
    -Kevin Kling

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.perforce.com/pipermail/perforce-user/attachments/19991020/6d4f4a64/attachment.html>