Share, Vote, & Discuss Ideas

We're constantly looking for new ways to improve our products and are asking you to help us by sharing your own ideas, voting for ideas you like, and discussing them with the rest of the community.

p4 proxy cleans itself automagically and then preloads with a defined clientspec

p4 proxy requires manual maintence to clean. It doesnt clean itself out of the box. To clean the cache you must stop p4p, clean the cache, start the proxy. Or write your own script to stop, clean and then restart p4p. Once manually cleaned or scripted clean you have to re-populate the cache again either manually or again via a script. Why cant this be inbuild as its so simply to improve out the box experience? (and for those who forget to clean the cache and wonder why things stop working :) Id like to see it automagically cleans itself either after so many days or when it reachs a threshold of so many GB's full or % full or there is only so many GB's free / or % free on the disk. Or files which havent been touched in the last X days etc you get the idea... Also in addtion to cleaning out the cache it then preloads with a defined client spec. Something along the lines of : p4p -clean 10 days -prefetch clientspec1 or p4p -limit 50GB -prefetch projectspec1,customclientspec2 or p4p -keeppercentfree 10 -prefetch largeprojectclientspec10 Surely an easy win here?
  • Guest
  • May 29 2015
  • Attach files
  • Jean-François Martin commented
    June 1, 2017 15:20

    Although I would like to have that built-in (I just voted for it), I would just like to point out that you do not have to stop the Proxy when cleaning it. You should however delete pdb.lbr once done.


    The way we handle this at work is making sure the mount updates the atime and then do a find job based on days and delete the ones over that threshold.