https://bugzilla.novell.com/show_bug.cgi?id=207611 ------- Comment #24 from admin@eregion.de 2006-10-17 12:22 MST ------- hm. pippin:/var/log # head -1 zmd-backend.log; tail -1 zmd-backend.log; du -sch zmd-backend.log 2006-10-17 20:08:15 <1> pippin(13231) [parse-metadata] parse-metadata.cc(main):139 ------------------------------------- 2006-10-17 20:14:09 <1> pippin(16328) [media] MediaManager.cc(restoreAutoMounter):248 Restored HAL volume handling (automounter) 2.7M zmd-backend.log close to 3 megs, just for starting zmd... and the content looks like zmd is still stuck on log-level=debug even when configured for "fatal"... And to put it out in the open, with log-level=fatal i expect nothing else than a timestamp like for starting zmd, a timestamp for stopping, and a line whenever an action fails to complete. For example, when zmd hits a 404 when getting a rpm file. nothing more. but still, its an improvement. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.