Le 20/12/2016 à 18:24, Andrei Borzenkov a écrit :
20.12.2016 19:55, jdd пишет:
what I see id that syslog uses a special file for leafnode.
It CAN BE CONFIGURED BY ADMINISTRATOR to use special file for leafnode. That is exactly what is not possible with journal.
really? I don't use leafnode, but don't see why the official instructions couldn't work, even is that mean use an other system than journalctl logs
You still can use that and don't use the standard log system for debugging purpose
Which rather defeats the very idea of having standard log system in the first place.
why? the old way still ask to use a special file Not to mention that this presumes "debugging" is something
performed by developers only. In reality I have to deal with those logs every time I investigate problem on customer systems. They are extremely helpful in finished programs, the more logs - the better. But you also have no reasons to keep them for years.
and? they have to be used by admins. Anyway, It's unuseful to discuss this very problem only. debug mode is pretty common and everybody know it can generate a lot of logs. So the question on subject should be really: "how to manage debug mode" and not challenge what is one of the main journalctl feature (binary). I don't see neither why a debug mode should be kept for month if the logs are not analyzed in details. We should really focus on trying to solve real problems, not imaginary ones nor try to promote not viable solutions thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org