[p4] Trigger to limit size of files being added

[Stephen Vance]

A change-content trigger should be able to inspect the size of the file. 
Or you could just use protections to block zips for all but a select 
handful of users. Another alternative is to give all zips, or maybe all 
zips in particular locations, the +S modifier so that no more than a 
revision (or more if you use the argument) are stored. What are the 
reasons people are checking these in? Ignorance? Process optimization?

Steve

Jamison, Shawn wrote:
> I recently had a years worth of disk space vanish in 2 months and while
> investigating I found users were checking in 100 MB to 300 MB zip files.
> Some of these had 20 revisions.
>
> I also had a user place a 600 MB ISO image into perforce.
>
> Does anyone know of a way to prevent large binary files from being added
> or checked in to Perforce?
>
>
> Thanks
> -Shawn Jamison>
> Ciena Corp.
> Perforce Admin
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>   

-- 
Stephen Vance
www.vance.com