You might want to quickly look through http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#shared-state-cache in the ref-manual before supplying raw documentation information. This section is our current discourse on sstate.
Scott >-----Original Message----- >From: yocto-boun...@yoctoproject.org [mailto:yocto- >boun...@yoctoproject.org] On Behalf Of Paul Eggleton >Sent: Monday, February 02, 2015 9:43 AM >To: Burton, Ross; Christopher Larson; Gary Thomas >Cc: yocto@yoctoproject.org >Subject: Re: [yocto] sstate management > >On Monday 02 February 2015 17:33:23 Burton, Ross wrote: >> On 2 February 2015 at 16:48, Christopher Larson <clar...@kergoth.com> >wrote: >> > Is there some maintenance to be done on the sstate-cache? >> > >> >> I'm thinking I want to set up a shared cache which might >> >> last for a long time and I would like to only keep the bits >> >> that are really needed. >> > >> > In the past i've either used sstate-cache-management.sh or ensured >> > that SSTATE_DIR is on a mount with atime enabled and just >> > periodically wiped anything that hasn't been accessed in over a week. >> >> Seconded on this - after doing lots of builds in the last few weeks >> involving five machines and new eglibc/gcc patches my sstate was >> 1.2TB. A quick find -atime -delete did the job. > >I don't suppose I can talk one or more of you into writing up some >documentation for this to add to the manual? (As usual, something raw in the >form of a wiki page that Scott can then adapt would be ideal.) > >Cheers, >Paul > >-- > >Paul Eggleton >Intel Open Source Technology Centre >-- >_______________________________________________ >yocto mailing list >yocto@yoctoproject.org >https://lists.yoctoproject.org/listinfo/yocto -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
