Same content, different names of 2 or more files –– how to identify the duplicates?
Use check sum utilities (like chksum, md5sum, sha1sum, …) for this, and sort on their output!
Category: UNIX
-
linux – how to ‘grep’ a continuous stream
- http://stackoverflow.com/questions/7161821/how-to-grep-a-continuous-stream
- I had never heard of “stdbuf” before
- AIX grep has -u
- GNU grep has –line-buffered, its -u is not the same as AIX grep’s
-
logcheck – scans your logfiles and warns you
- www.logcheck.org
- sourceforge.net/projects/logcheck/
- linuxaria.com/pills/logcheck-scan-your-logs-and-warns-you – this is the nicest overview page
Dependencies and restrictions:- logcheck depends on logtail
- logtail runs on exactly one file …
- … and only once on that file, as it keeps a sister file called logfile.offset
- improving this should actually be “easy”, e.g. keeping a sister file called logfile.offset.user
Pros:- abstracting resp. filtering log files like /var/log/messages
- this happens “realtime” i.e. instantly
- …
Cons:- the results get to you resp. a whole crowd via e-mail – isn’t that a little excessive regarding the resources necessary to look at the output?
- if you already have a utilty in place, that filters daily chunks of log files, this is …
- …
Ideas / inspirations taken from here:- the output could actually go to another log file, that you may want to “logtail” or “tail -f” as to your needs
- …
-
AIX has a limit for cronjobs concurrently being run
Sounds reasonable in a way. But it’s rather bad, if you are not aware of it, and your corporate OS Monitoring Services do not remind you of critical entries in the resp. cron log file. They may say something like:
there is crontab entry, that did not get executed, because we exceeded the maximum number of … – maybe you want to fix something here
I suppose, similar limits exist in every UNIX flavour.