Yesterday when extracting a ZIP file created with WinRAR I received dozens of errors during the process. The file I was extracting was generated from the entire Documents and Settings folder on a Windows XP computer and I was extracting it to the Desktop of another user on another computer. The issue is the fact that the path and/or filename exceeded the 260 characters which is set by WinRAR. Below I show some output from the errors received as well as two tips that should help resolve the problem.
The rar command can be useful on Linux to not only compress a file but also split the file into multiple parts during the compression. This will make the files easier to transfer to other servers or easier for other people to download. First rar needs to be installed which can done on CentOS using the directions below. After that we describe how to easily compress and break a file into multiple chunks using one simple rar command.
Working on a friends server earlier this morning I noticed that he had logrotate configured but he did not have a configuration file for Postfix. Below is the quick one I whipped up for his environment including a brief explanation of each line of the configuration file below the script. Following the explanation of the various configurations is the command to actually force logrotate to run in debug mode so you can see what happens.
I needed to clean up a directory on a server that included numerous directories each with numerous files inside each directory. I decided to write a quick shell script that would archive with tar and then compress with bzip2. The shell script requires you pass in a variable which could technically just be “*” to include all directories in the directory you are running the script from. Below is the content of the script followed by an explanation of each line of the script that will archive and compress numerous directories by looping through each directory to create a .tar.bzip2 file.
It can be beneficial sometimes to search for patterns in files on a Linux server that have been compressed with gzip instead of having to uncompress each file to search through it. A good example of this if typically in log rotation you rotate the logs and compress the older log files so if you are troubleshooting an issue and need to search for an error in older log files you could use the method below to search the compressed log files to match a pattern without having to uncompress each log file.