| Date Of Receipt: 9-MAY-1996 00:22:51.22
From: HUNCH::"vandyck@cardinal.zk3.dec.com"
To: krueger@seedy.mro.dec.com
CC: adm@zk3.dec.com, odehelp@zk3.dec.com,
kauffman%cespul.dnet.dec.com@seedy.mro.dec.com
Subj: Re: supping pthw1os.nightly
In case you missed it, about a week or two ago pthw1os became ptaos, thus your
inability to sup the non-existant pthw1os.nightly. I left some symlinks in
place for the submit tree during this transition, which is why pthw1os still
works. Although they will go away soon.
For OS (and I think that's probably all you care about) you'll need ptaos and
it's nightly tree, as well as ptos.bl11 - this week - and ptos.bl12 next week.
-Grant
>
>
>
> Hi,
>
> I've been requested to start sup'ping the pthw1os pools. The
> submit tree pthw1os_pool seems to be coming down without problem
> but the pthw1os.nighty_pool hasn't been sup enabled yet. Could
> somebody please setup the sup list for pthw1os.nightly_pool?
>
> On a related subject when working from a remote site, like we
> do in shr, we have no problem doing builds, bco's and bci's with
> a small local subset of the backing trees that are in zk. However,
> in the past when it has come time to do a bsubmit a whole bunch
> of backing trees have been required to be present locally. It
> generally comes as a rude suprise and I scramble about finding
> which backing trees need to be sup'ed and locating local space to
> put them. Could you tell me at this point which backing trees
> it's necessary to have locally so that people down here can do
> bsubmits to pthw1os?
>
> Thanks,
>
> -Ron
>
> ----------------------------------------------------------------------------
> Ron Krueger enet: Helix::Krueger
> Real-Time Software Engineering inet: krueger@osfrt.shr.dec.com
>
>
>
--
Grant Van Dyck enet: vandyck@zk3.dec.com
Release Engineering
|