agarrharr/awesome-cli-apps

-
GitHub - agarrharr/awesome-cli-apps: 🖥 📊 🕹 🛠 A curated list of command line apps https://share.google/84umtb3QdZIBiyxOm

Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more

Selecting DataStage job log results in error: Error Selecting from log file RT_LOG

-
​ Problem(Abstract) When trying to view a job log in DataStage Director, an error similar to the following is received: Error selecting from log file RT_LOGnn Command was: SSELECT RT_LOGnn WITH @ID LIKE '1NON' COUNT.SU Error was: Internal data error. File <path_to>/RT_LOGnn/<filename>': Computed blink of 0xnnnn does not match expected blink of 0xnnnn! Detected within group starting at address 0xnnnnnn! Cause The error message received indicates that the log file for the job is corrupted. Resolving the problem To resolve the problem, the log file must be discarded and recreated. There are a number of ways to accomplish this. Reimport the job and overwrite the existing job. Rename the job or do a File-->Save as in Designer. You can then delete the old job and rename your new job back to the original name. Manually recreate the RT_LOGxxx file. Note: The job with the associated RT_LOG may need to be re-compi...
Read more