On 30.06.2016 19:42, Martin Babinsky wrote:
On 06/30/2016 01:54 PM, Martin Basti wrote:
On 30.06.2016 12:07, Petr Spacek wrote:
On 30.6.2016 10:21, Jan Cholasta wrote:
On 30.6.2016 10:12, Petr Spacek wrote:
On 30.6.2016 10:14, Jan Cholasta wrote:
On 30.6.2016 10:06, Petr Spacek wrote:
On 30.6.2016 10:02, Jan Cholasta wrote:
On 30.6.2016 09:56, Petr Spacek wrote:
"The easiest solution would be to add timestamps to logs, or
On 30.6.2016 09:40, Martin Basti wrote:
logs from oddjob or from installer
Actually the easiest solution would be not to log into a file
Well, IPA is hard enough to debug even with logs. I would not make
even worse by not logging at all :-)
The commands logs into stderr, and both stdout and stderr are sent
back to the
caller of the oddjob.
Alternatively, it could log into a different file (say
/var/log/ipareplica-conncheck-oddjob.log). IMO timestamps are an
fix this bug.
When we are at it, a custom logger is overkill. IMHO we should log
to journal and be done with it ...
It's not, we want to log to at least stderr ourselves.
Also, it would be even harder to implement than timestamps, and time
Sure, we do not have time:
=> ACK for current version of the patch.
factor here. It would fit more into
I would rather use timestamp format with dashes between numbers
to make it
easier to read and parse for humans.
New patches attaches
Works for me, ACK.
* 4ce0258c235c985e07a19d291bd699720d9ef1bf Add option --no-log for
* 08fcc7e25af54379eec87f4e22f8cd26db7ffbb0 Do not log to file in remote
Manage your subscription for the Freeipa-devel mailing list:
Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code