On 05/03/2013 09:07 AM, Jiri Srain wrote:
Hi Roberto,
in principle, there is nothing that prevents always logging in the debug
mode. However, you should be aware that the amount of data being logged
is huge. This has following implications:
- as the logs are stored in ramdisk during installation, the memory
requirements for installation may go up slightly
- the amount of data written to the log may hit the installation time,
especially in 2nd stage (writing directly to disk)
- (probably worst) the log will need to rotate - meaning that at the end
of the installation, the logs from the beginning may not be available
any more
Especially the last one may mean that in the end you don't resolve
customer's problem, but even make it worse for us to obtain the right
part of the log.
And I have some more "why not to do that":
- The amount of logs in debug mode comparing to normal mode is that
much bigger that is almost impossible to find what you are looking
for when looking for possible errors reported in logs.
- It's true that I don't have the `data` but I don't think most of the
time Y2DEBUG is required by SUSE engineers. Frankly, I personally
don't want it almost ever.
- Debugging definitely slows down the execution time as the application
is always waiting for disk / memory / swap to write the log,
especially on some HW such as S/390.
Bye
Lukas
--
Lukas Ocilka, Cloud & Systems Management Department
SUSE LINUX s.r.o., Praha
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
