On Dienstag, 27. Januar 2009, Roberto Angelino wrote:

Yast Developers, My customer has setup an autoyast installation (sles10 sp1) and it works great. The problem is log messages are output to the physical console AND over SOL (Serial Over LAN). This SOL connection is 9600 baud (please don't ask me to tell them to increase--they can't) so the installation can take quite a while because of all the text yast is spewing over this 9600 connection can take some time. They are asking if there's a way to reduce it or eliminate it?

Look here: http://forgeftp.novell.com/yast/doc/SL11.1/tdg/yast2-logging.html "1.2.9. Logging control" HTH -- Stefan Hundhammer Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

On Donnerstag, 29. Januar 2009, Roberto Angelino wrote:

   Customer is asking question with respect to the display, not the log file. So during installation, the rpms are filying by in the little dialog window with progress bar.  Is there a way to limit that output?  Or even the display period?

Ah, you mean the output to that NCurses window that displays the package name and description as each one is installed, not the log. Sorry, I had misunderstood that. AFAICS, the only way to suppress that output would be to patch some YCP code , and I don't think this is an option for an end user. Even worse, the relevant code is all in YCP modules which are byte-compiled on the installation media, so that byte code would have to be regenerated after patching the YCP code. I don't think this can realistically be done. But is that output really a performance bottleneck? Or is it more a "gut feeling" that this customer has? The NCurses library is really efficient at that: For every screen operation, it sends only the difference between the old screen content and the new screen content to the terminal (plus escape sequences to position the cursor etc.). CU -- Stefan Hundhammer Penguin by conviction. YaST2 Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Stefan Hundhammer wrote:

The NCurses library is really efficient at that: For every screen operation, it sends only the difference between the old screen content and the new screen content to the terminal (plus escape sequences to position the cursor etc.).

Hi, Maybe if it comes to "initializing the sources..." - downloading several files withs lots of Progress screens - then it sends quite of lot of screen changes per second. Maybe I'm wrong but this is my feeling from how I understand Roberto's question. Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.