https://bugzilla.redhat.com/show_bug.cgi?id=1304882 --- Comment #28 from awilliam@xxxxxxxxxx <awilliam@xxxxxxxxxx> --- So we can achieve fairly simple logging to the journal simply by setting the log 'file' setting to nothing at all in config: file = or making it undefined it in the code block that defines the 'defaults'. this causes Mojo to log to stderr, and the journal picks that up. The log message levels aren't picked up by journald when you do it this way, but it's good enough for now I think. A sysadmin can still easily log to file by setting `file` in openqa.ini. I've written a simple patch to change the default in this way and sent it upstream for discussion, and done a 4.3-10 build with the change: https://github.com/os-autoinst/openQA/pull/541 https://www.happyassassin.net/reviews/openqa/openqa.spec https://www.happyassassin.net/reviews/openqa/openqa-4.3-10.fc23.src.rpm https://www.happyassassin.net/reviews/openqa/4.3-9_4.3-10.diff https://koji.fedoraproject.org/koji/taskinfo?taskID=12934037 I wasn't citing Wordpress the project, but wordpress the package ;) It's one of our older and more heavily used webapp packages, so I tend to consider it a reasonable example spec. Yeah, I believe that avoiding nesting should avoid the attack vector. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review