Make emerge log to syslog. Very important for auditing, affects security if people go around installing things without syslog capturing it (local logs are insufficient for centralized alerting). PORTAGE_ELOG_SYSTEM is not emerge logging. See yum for a proper example of how this should be done.
There was a bug about 4-5 years back on this, the result of which was the dev couldn't be bothered to make this right. Please do not mark this as a duplicate. That bug was closed for the wrong reasons. In this day and age it's an absolutely terrible practice to not log everything to syslog.
With syslog-ng it's trivial to integrate emerge.log with the system log: ---- /etc/syslog-ng/syslog-ng.conf source emerge { file("/var/log/emerge.log"); }; ... log { source(emerge); filter(...whatever...); destination(...whatever...); }; -------- Granted, some loggers may lack this capability, but choosing a suitable logger seems more apropos than adding syslog integration to Portage. Not everyone wants or needs that.
This is a workaround that shouldn't be necessary. So, we are to maintain separate logging configurations for Gentoo distribution systems to make up for a very obvious deficiency in portage logging? It is more correct and appropriate for applications to log correctly that to start making workarounds here and there which soon add up and lead to more difficult maintenance as things become more and more disparate. I'd prefer to see more standardization than tacked on workarounds.
> This is a workaround that shouldn't be necessary. > > So, we are to maintain separate logging configurations for Gentoo distribution > systems to make up for a very obvious deficiency in portage logging? I wouldn't call it obvious or a deficiency. > > It is more correct and appropriate for applications to log correctly that to > start making workarounds here and there which soon add up and lead to more > difficult maintenance as things become more and more disparate. I don't think you can really agree on what 'logging correctly' means. That being said I got bored today and wrote a patch for this; so expect it soon. -A
We can add support for FEATURES=syslog or maybe an emerge --syslog option that you can add to EMERGE_DEFAULT_OPTS.
(In reply to comment #5) > We can add support for FEATURES=syslog or maybe an emerge --syslog option that > you can add to EMERGE_DEFAULT_OPTS. > I think, it will be better to return oprability of 'syslog' option of 'PORTAGE_ELOG_SYSTEM' parmetr in /etc/make.conf.
Ping? Portage should be able to log to syslog, this is standard practice on *nix systems.
(In reply to comment #6) > I think, it will be better to return oprability of 'syslog' option of > 'PORTAGE_ELOG_SYSTEM' parmetr in /etc/make.conf. That should be working now. I tested it myself when I fixed bug 390965. (In reply to comment #7) > Ping? Portage should be able to log to syslog, this is standard practice on > *nix systems. If you'd like to submit a patch, you can use the code from /usr/lib/portage/pym/pym/portage/elog/mod_syslog.py for example. I would make it conditional on FEATURES=syslog.
