RE: [cobalt-developers] Corrupt Packages

["Byron C. Servies" <bservies@xxxxxxxxxx>]

On 2/12/01 at 1:36 PM, wes@xxxxxxxxxxxxxxxxxx (Wesley A. Schiesz) wrote:

> Kal,
> 
> I must agree, I am not seeing any log files generated in the /home/tmp
> folder at all during the install process.
> 
> Byron: Must we configure something to provide output?
> 
> We are creating .pkg files from scratch so I can eliminate the transfer
> corruption. We simply recreated the sample package files, altered them for
> our app, and created a compressed tar archive. Placed them into
> /home/packages and then loaded them from the UI. They consistently read
> Corrupt Package.
> 
> Our application runs 175mg + as a .pkg that is compressed. Is there a
> timeout on the install function of the Cobalt UI ?

I'm working from memory here, so I may have the location of the directory wrong. 
Unfortunately, I don't have a raq4 to test with today (can you believe it?  I'm
snowed in in California!).  It is certainly under /home though.  AFAIK, there is
no way to turn off the log process.

When I test, I use the UI to transfer the package to the machine as well, and the
largest package I've attempted to install is 13MB.

Take a look in /usr/local/sbin/cobalt_upgrade (or similar script, I'm working from
a qube2 here, which may be different.  Sorry) and see if you can identify the
logging directory.

Sorry for shooting from the hip.

HTH,

Byron