Creation Password prompt

[bruce at stn.com]

Quoting Enrique Arredondo <henry at vegena.net>:
> 
> 
> ----- Original Message ----- 
> From: "Joe Chasan" <joe at magnatechonline.com>
> To: <filepro-list at lists.celestial.com>
> Sent: Friday, February 09, 2007 1:21 PM
> Subject: Re: Creation Password prompt
> 
> 
> > On Fri, Feb 09, 2007 at 03:53:00PM -0500, Fairlight wrote:
> >> When asked his whereabouts on Fri, Feb 09, 2007 at 12:48:09PM -0800,
> >> Enrique Arredondo took the fifth, drank it, and then slurred:
> >> > Hi,
> >> >
> >> > I'm moving a database from one old SCO box to my current one but
> after
> >> > copying all the files using ftp  to the new box , I get this prompt
> all
> >> > the time:
> >> >
> >> > Enter Creation Password for 'bay.WRITEUP'
> >> >
> >> > How can I get rid of that prompt ?
> >>
> >> If it's what I think it is, grab the extra field from
> /etc/default/fppath
> >> and put it in the new one.
> >
> > no, its the site password that is stored there.
> >
> > if he's getting prompted for a creation password on files that he was
> > not getting before, chances are something got corrupted in the copy,
> > so the question is how did he copy all the files via ftp to the new
> > box.
> >
> > for something like this, personally, i'd make up a tarball of the
> > directory/directories, compress it with the best compression utility
> > the 2 boxes have in common, ftp the compressed tarball, then
> > uncompress/restore to proper directory on new box.   if the tarball
> > is small, skip the compression step.
> >
> 
> I copied all of the files using tarball, and still getting the damn
> "enter 
> creation password" , I copied from an SCO unix old machine into REDHAD
> linux 
> filepro installation and it works flawless, but then after I tar and
> move 
> from linux to the New SCO 5.0.7 box I start getting all the errors. I
> wonder 
> if the restore I did on the linux from tape was the trick to success ?
> 
> 

I seem to remember having some problem like this where the default blocking 
factor for tar on the Red Hat was not the same as the SCO and causing tars to  
not be built and then undone as expected.  This may have nothing to do with 
it, but I know I had a problem lke that recently.  I think on the SCO to see 
what is used  you look at the file /etc/default/tar, whereas in Red Hat, I 
think the man page shows the default factor being used.  I remember having to 
use the tar command with a flag to set the default for Red Hat to the same 
factor used by SCO when tarring up the file.  We may have only noticed 
problems on large files - and come to think of it, I don't remember creation 
passwords being a problem, so this is just a guess.

Bruce

Bruce Easton
STN, Inc.