Re: Linux - IIF2000
Posted in 2000
Hi,
I encountered a similar problem on RedHat 6.1 about six months ago. I
used the wrong options on the cpio command when extracting the database
files. After deleting and using the correct cpio commands it worked
fine.
This is an extract of an old email I have:
>>Linux cpio is picky.
>
>It is.
>
>>I think it might be trying to use the wrong POSIX version of '-c'.
>
>POSIX never standardized cpio; it created PAX instead. No-one ever uses
>pax (including me); few have even heard of it, but it's there in
>/usr/bin on Solaris 2.6, but is not available on Linux.
>
>>Try it without the 'c' option, i.e.:
>> cpio -ivdumB < ?filename.cpi? >
>
>That should work. On Solaris etc, you need to create the cpio file with
>the '-c' option; on Linux, you need to read the 'character CPIO' file
>without the '-c' option. On Linux, the '-c' option is documented as
>'Use the old portable (ASCII) archive format.' It is also documented as
>supporting "the following archive formats: binary, old ASCII, new ASCII,
>crc, HPUX binary, old ASCII, old tar and POSIX.1 tar.' The Linux cpio
>automatically detects the correct cpio format when reading the archive.
>You can override this on input or output with the '-H FORMAT' or
>'--format=FORMAT' options. Read the man page for more details.
Thomas Parsli wrote:
>
> "Martin Beran" <idc_ln@telecom.cz> writes:
>
> > Hello,
> >
> > I have installed SuSE6.4 and IDS 9.20.UC1. When I set Informix parameters
> > with 'onmonitor', database server goes to 'online' mode and everything works
> > normaly.
> > After restart server (onmode -ky ... oninit) operating system full crash
> > without any error message.
> > When I delete cooked file, touch new and repeat in 'onmonitor' setup of
> > parameters, everithing is ready again.
> >
> > Can you help me, please?
>
> Others have complained about Informix crashing on Suse, but running
> fine on RedHat. You'll probably find one in this group if you search
> with (i.e) deja.com
>
> There's probably a problem with glibc and you "could" locate that problem
> by running oninit via strace and read some thousand lines of tracing...
> (...or you could ditch Suse and run RedHat;)
>
> Thomas