Re: [p4] Broker config: Cannot get version to match

I totally forgot about the "version"!
Yes, we have this in our broker config file:
command: ^.*$
{
    prog    = P4V/NT;
    version = v7[1234567];
    action  = reject;
    message = "Your client software is too old.\nPlease reinstall P4V: http://wiki/Perforce_Quickstart#Windows";
}

You also asked in the other message:
> How did you ' reject the "most popular" versions'?

We grep for P4V lines in p4d logs and uniq'ify them by the versions.
In our case, we had something like 4-5 different versions.
Then, we sent email to the users asking to upgrade or uninstall P4V.
(We highly recommend installing P4V downloaded internally - not from the Perforce site. Otherwise, users will be running non-qualified versions. We don’t enforce it exactly - except the case below - but users know they will possibly shoot themselves in the foot otherwise.)

We have a simple wrapper script around the installer, which is what our users run to install P4V.
Our IT department forcefully runs that script on users machines if the version of the installed P4V is prior to X (this value changes as we qualify/approve a new version).
It took us a little while, but we now don’t have the problem with the old unacceptable versions.

--
Michael Mirman
MathWorks, Inc.
3 Apple Hill Drive, Natick, MA 01760
508-647-7555

> -----Original Message-----
> From: perforce-user [mailto:[email protected]] On Behalf
> Of roadkills_r_us
> Sent: Friday, October 06, 2017 2:00 PM
> To: [email protected]
> Subject: Re: [p4] Broker config: Cannot get version to match
> 
> Posted on behalf of forum user 'roadkills_r_us'.
> 
> Randall Fong with P4 support (I opened a case) sent the solution below. I
> haven't tried the P4D config par because the broker config worked fine. (We
> do as much at the broker as possible to keep the server load lighter.)
> 
> Try:
> command: .*
> {
> prog = P4V\/.*\/2015\/.*;
> version = v81;
> action = reject;
> message = "You must use a 2017.1 or later client. If you need help
> upgrading your client, please file a ticket";
> }
> 
> as seen in "The syntax of the broker command handler conditions" KB
> attached.
> 
> Or, better yet, use rejectList as seen in "How to Use the
> 'rejectList' Feature to Reject Client Connections -
> http://answers.perforce.com/articles/KB/15014How  to Use the
> 'rejectList' Feature to Reject Client Connections"
> 
> 
> 
> --
> Please click here to see the post in its original format:
>   http://forums.perforce.com/index.php?/topic/5505-broker-config-cannot-get-
> version-to-match
> _______________________________________________
> perforce-user mailing list  -  [email protected]
> http://maillist.perforce.com/mailman/listinfo/perforce-user
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user