vaeth / logclean Goto Github PK
View Code? Open in Web Editor NEWKeep only compressed logs of installed packages (for Gentoo's portage system)
Home Page: http://www.mathematik.uni-wuerzburg.de/~vaeth/gentoo/index.html#logclean
logclean's People
Contributors
Stargazers
Watchers
logclean's Issues
uninitialized value $mtime
I just got this after an emerge:
Use of uninitialized value $mtime in integer subtraction (-) at /usr/bin/logclean line 699.
support for split-log and split-elog
I have a request to have logclean run recursively inside the log and elog directories in order to support the split-log and split-elog portage feature.
See https://wiki.gentoo.org/wiki/Portage_log for reference.
Do not execute logclean in case the options contain an error
I executed logclean -c -s logs instead of logclean -c '' -s logs and unintentionally, all my logs were cleaned. I would like to suggest to first check the options for errors and aborting when they contain errors.
Furthermore, no logfiles were retained, not even the most recent one for installed packages. (Only those for logclean and its dependencies.) As far as I could gather, no time-based cleaning should be done by default.
logclean wants to also clean out the log of the most recent successful install
As far as I understood, logclean should leave the log of the most recent successful install of a package. However, if I run logclean -s logs, I see that first all ‘old’ logs are rmed, but then logclean seems to go over the whole tree again and also rms the ‘recent’ logs. For example, for the kitty package, I get in the first part of the output
rm /var/log/portage/build/x11-terms/kitty-0.12.3:20181001-195923.log
rm /var/log/portage/build/x11-terms/kitty-9999:20180616-123918.log
rm /var/log/portage/build/x11-terms/kitty-0.13.1-r1:20181216-215738.log
rm /var/log/portage/build/x11-terms/kitty-0.11.2:20181001-200010.log
rm /var/log/portage/build/x11-terms/kitty-0.10.1:20180608-202438.log
rm /var/log/portage/build/x11-terms/kitty-0.11.2:20180726-082006.log
rm /var/log/portage/build/x11-terms/kitty-0.13.3:20190123-201330.log
rm /var/log/portage/build/x11-terms/kitty-0.10.1:20180609-201339.log
rm /var/log/portage/build/x11-terms/kitty-9999:20180616-124130.log
rm /var/log/portage/build/x11-terms/kitty-0.13.2:20190106-203835.log
rm /var/log/portage/build/x11-terms/kitty-0.13.1:20181212-215158.log
rm /var/log/portage/build/x11-terms/kitty-0.12.3:20181212-215234.log
rm /var/log/portage/build/x11-terms/kitty-0.13.1:20181216-215818.log
rm /var/log/portage/build/x11-terms/kitty-0.13.1-r1:20190106-203919.log
rm /var/log/portage/build/x11-terms/kitty-0.13.2:20190123-201411.log
rm /var/log/portage/build/x11-terms/kitty-0.14.2:20190616-173456.log
rm /var/log/portage/build/x11-terms/kitty-0.13.3:20190616-173542.log
rm /var/log/portage/build/x11-terms/kitty-0.14.4:20190901-111109.log
rm /var/log/portage/build/x11-terms/kitty-0.14.2:20190901-111149.log
rm /var/log/portage/build/x11-terms/kitty-0.14.6:20190929-150027.log
rm /var/log/portage/build/x11-terms/kitty-0.14.4:20190929-150125.log
rm /var/log/portage/build/x11-terms/kitty-0.14.6-r1:20191119-191303.log
rm /var/log/portage/build/x11-terms/kitty-0.14.6:20191119-191351.log
rm /var/log/portage/build/x11-terms/kitty-0.15.0:20191203-204758.log
rm /var/log/portage/build/x11-terms/kitty-0.14.6-r1:20191203-204849.log
rm /var/log/portage/build/x11-terms/kitty-0.15.0:20200109-195618.log
In the second part of the output, I get
rm /var/log/portage/build/x11-terms/kitty-0.15.1:20200109-195521.log
I would expect that the second part of the output is not present. What is going on? How can I make sure that the logs for the most recent successful installation will be kept?
N.B.: For firefox, the first part of the output contains the logs for old package versions and the second part contains the logs for the currently installed version, but there are two logs, as it had been reinstalled. That may give a clue to why there are apparently two ‘runs’ through the tree.
FYI, the directory listing:
# ls -alh build/x11-terms/
total 956K
drwxr-xr-x 1 root root 1.8K 9 jan 20:56 .
drwxr-xr-x 1 root root 1.7K 31 jan 14:26 ..
-rw-rw---- 1 portage portage 47K 8 jun 2018 kitty-0.10.1:20180608-202438.log
-rw-rw---- 1 portage portage 36 9 jun 2018 kitty-0.10.1:20180609-201339.log
-rw-rw---- 1 portage portage 58K 26 jul 2018 kitty-0.11.2:20180726-082006.log
-rw-rw---- 1 portage portage 19K 1 okt 2018 kitty-0.11.2:20181001-200010.log
-rw-rw---- 1 portage portage 53K 1 okt 2018 kitty-0.12.3:20181001-195923.log
-rw-rw---- 1 portage portage 14K 12 dec 2018 kitty-0.12.3:20181212-215234.log
-rw-rw---- 1 portage portage 37K 12 dec 2018 kitty-0.13.1:20181212-215158.log
-rw-rw---- 1 portage portage 14K 16 dec 2018 kitty-0.13.1:20181216-215818.log
-rw-rw---- 1 portage portage 56K 16 dec 2018 kitty-0.13.1-r1:20181216-215738.log
-rw-rw---- 1 portage portage 14K 6 jan 2019 kitty-0.13.1-r1:20190106-203919.log
-rw-rw---- 1 portage portage 55K 6 jan 2019 kitty-0.13.2:20190106-203835.log
-rw-rw---- 1 portage portage 14K 23 jan 2019 kitty-0.13.2:20190123-201411.log
-rw-rw---- 1 portage portage 55K 23 jan 2019 kitty-0.13.3:20190123-201330.log
-rw-rw---- 1 portage portage 14K 16 jun 2019 kitty-0.13.3:20190616-173542.log
-rw-rw---- 1 portage portage 60K 16 jun 2019 kitty-0.14.2:20190616-173456.log
-rw-rw---- 1 portage portage 28K 1 sep 13:11 kitty-0.14.2:20190901-111149.log
-rw-rw---- 1 portage portage 48K 1 sep 13:11 kitty-0.14.4:20190901-111109.log
-rw-rw---- 1 portage portage 28K 29 sep 17:01 kitty-0.14.4:20190929-150125.log
-rw-rw---- 1 portage portage 48K 29 sep 17:01 kitty-0.14.6:20190929-150027.log
-rw-rw---- 1 portage portage 28K 19 nov 20:13 kitty-0.14.6:20191119-191351.log
-rw-rw---- 1 portage portage 48K 19 nov 20:13 kitty-0.14.6-r1:20191119-191303.log
-rw-rw---- 1 portage portage 28K 3 dec 21:48 kitty-0.14.6-r1:20191203-204849.log
-rw-rw---- 1 portage portage 50K 3 dec 21:48 kitty-0.15.0:20191203-204758.log
-rw-rw---- 1 portage portage 35K 9 jan 20:56 kitty-0.15.0:20200109-195618.log
-rw-rw---- 1 portage portage 50K 9 jan 20:56 kitty-0.15.1:20200109-195521.log
-rw-rw---- 1 portage portage 1.6K 16 jun 2018 kitty-9999:20180616-123918.log
-rw-rw---- 1 portage portage 20K 16 jun 2018 kitty-9999:20180616-124130.log
clean more escape sequences
stuff like this �[32;01m * �[39;49;00m doesn't get cleaned
see https://gist.github.com/Alessandro-Barbieri/6628c59a3b60913627363bee10da599c
for an example
in-place uncoloring
Is it possible to automatically uncolor the .log files and replace the original with the uncolored version?
I see that by default it uncolor and compress but the original stay as is (the original will be deleted later e.g. after 24 hours)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.