1848619 Members
5845 Online
104033 Solutions
New Discussion

Ignite/UX install.log

 
Frank Fitch_1
Advisor

Ignite/UX install.log

I am running Ignite/UX 3.7.95. I have been mildly annoyed over the past few years with the seeming time lag associated with updates to the install.log file during an ignite, i.e. it appears that output to the logfile is buffered for some period of time before it is actually written to the file. Hence, one doesn't know what the ignition is doing minute to minute --- or if in fact it is doing anything at all. Is there a way to change the behavior of Ignite/UX to keep the install.log file more up to date ---- aside from stopping the install?

This may or may not be relevant, but I use ftp rather than nfs to copy gzipped archives from server to client. Also,I run v3.7.95 with the understanding(perhaps erroneous) that it is the last rev to support HP-UX 10.20. I perform via cron, make_net_recovery operations in a mixed environment of HP-UX 10.20 and 11.x systems. make_net_recovery requires that both server and client run the same version of Ignite --- hence I'm stuck at 3.7.95.

Any help would be appreciated, It's Friday 5:00PM EST and I have an Ignite that is seemingly running longer than it should. The last verbage in the install.log is not very enlightening..... It is:

* Loading_software: Begin

* Installing boot area on disk.
* Enabling swap areas.
* Backing up LVM configuration for "vg00".
* Backing up LVM configuration for "vg01".
* Backing up LVM configuration for "vg02".

lsof on the server shows my core archive as open, client disk light is blinking, NICs shows traffic, lanadmin shows nominal errors, GPM on server shows disk activity in the appropriate lvols. I sure wish that I knew how much of the archive has been downloaded.

Thanks for allowing me to rant and in advance for the help.......... Frank