terence.bodola at cbsparamount
Aug 14, 2008, 9:10 AM
Post #7 of 15
(811 views)
Permalink
|
you're right. it's just our stories that have multiple ocs. what is
happening is that since the non-primary story ocs haven't been repreviewed
(and having blown out our preview web server dir those original preview
files are gone) we are having preview problems with other stories that use
those story oc preview files.
can i repreview these from the other direction...like, can i repreview all
stories in an oc (previewing in that oc not the primary) using bric_soap?
so in tmp there is:
/usr/local/bricolage/tmp/usr/local/bricolage/comp/data/media <--that has all
the media dirs under it
/usr/local/bricolage/tmp/usr/local/bricolage/data/burn <--that has preview
and stage dirs under it, and they have the oc_* dirs under them
i want to blow out tmp b/c it is large...if the files will just be recreated
on use and nothing bad comes of it. i am a little wary now b/c of the pain
blowing out preview web dir caused. i thought media would just rebuild in
preview web dir upon repreview of stories that use the media, but that's not
right, and so when previewing a story you would now first need to go
repreview all media and stories used/included in it individually first (and
possibly non-primary ocs for those stories as well). you helped me fix this
problem for media with a bric_soap scripted repreview (thank you for that),
and it is mostly fixed for stories (it is fixed for primary oc)...just not
completely.
right now i backup the bric tmp dir (b/c i don't know if i can not do it)
and so it takes up a lot of space not just on the bric server but on the
backup servers as well (and since it changes a good bit i think it is making
our daily incremental backups much larger than they need be).
terence
On 8/14/08 8:34 AM, "David E. Wheeler" <david[at]kineticode.com> wrote:
> On Aug 14, 2008, at 06:35, bodola, terence wrote:
>
>> so then my next best option would be lwp or similar for repreviewing
>> all output channels for stories and media?
>
> Yeah. I find that it's pretty rare that media are in multiple OCs,
> though, since no templates get applied to them. Why are yours in
> multiple OCs?
>
>> i see that it says in the api browser that bric_clean_tmp cleans all
>> files in tmp older than 12 hours...but my installation doesn't seem
>> to do this when bric_clean_tmp is croned...and i don't think it is
>> some kind of atime issue...just doesn't seem to clean anything
>> (except maybe lock/session). so you are saying it is find to blow
>> out everything in /usr/local/bricolage/tmp/ ?
>
> No, I didn't say that. What's in that directory?
>
> It probably is fine, though all your users will be logged out
> afterward, and you should restart Bricolage after you delete it, too.
> Even better, shut it down, then clear out everything, then start up
> again.
>
>> i realize this will break all user sessions, so should boot everyone
>> from system first or not blow out lock/session files...but otherwise
>> ok?
>
> Probably. But why do you want to do this?
>
>> also, got a forbidden for the link at the bottom of that System
>> Administration -> Application section...the link to:
>> http://www.bricolage.cc/docs/current/api/Bric/?bric_clean_tmp
>
> Yeah, known issue. I'll be revamping the doc browser in the next few
> weeks and fixing those bugs.
>
> Best,
>
> David
>
|
