| Summary: | emerge.log could be managed by logrotate | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Peter Hyman <pete4abw> |
| Component: | Unclassified | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | enhancement | CC: | jakub |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | sample logrotate configuration file for pruning emerge.log | ||
|
Description
Peter Hyman
2006-02-07 02:27:59 UTC
Created attachment 79095 [details]
sample logrotate configuration file for pruning emerge.log
could be put in files/ in portage if desired. Feel free to modify or discard without attribution.
That would just break tools that rely on emerge.log being untruncated (like genlop). genlop is not a Gentoo-developed application. It's a tool some users may choose to use. You criticized me for making an ebuild (pyflac) that benefits one program (musicbox). Now, I suggest your rejection of this enhancement for ONE program is also unwarranted. I think you should let the portage devs decide. Reopening. Sigh... just rotate it yourself if you care so much about space, instead of breaking tools that are distributed in portage tree for no reason. # du -h /var/log/emerge.log 3.2M /var/log/emerge.log Wow, that's indeed huge, and FYI - this server has been installed on May 26, 2004. :P # du -h /var/log/emerge.log 2.6M /var/log/emerge.log The above installed Mar 19, 2005 and heavily used for testing. |
