Would files and files keep CHMOD?Access rights to files/catalogs retained by the programme tar Inside the archive, respectively, when the archive is sold, tar designates to each established file/catalogu the same rights that have been recorded inside the archives.Did the folder and files have a certain user owner?programme tar (at least project implementation) gnu(d) When establishing the archive, the owner/category/catalog remains information not only in numerical form (c)uid/gidbut also in the form of lines, so that the lines are not retained, we can use the option. --numeric-owner♪This information does not have (natural) influence when a single user can produce files/catalogues owned by him alone.at a sale launched on behalf of a super-user (in which case uid equal to zero; normally a line is designated as a name for the user rootthere is no such restriction: the process may create files/cataloges belonging to the user/group with any uid/gid♪Accordingly, if the archive retains the rows with the names of the owners/groups, the names will be used if there is a user/group with the name in the system where the package is performed.If there is no user name/group in the system (or names have not been retained at all due to the above-mentioned option --numeric-ownerthe numerical values stored in the archive will be used. uid/gid There may be very different lines with user/group names. You seem to be facing this situation.Disclosure, in fact, one: prior to sale, users/groups should be established in the system with the names retained inside the archives.You can see these names by adding an option. -v Look at the contents of the archive. -t$ tar -t -v -f архив Example of conclusion:-rw-r--r-- user/group 0 2016-11-11 12:41 file Which shows that the file file owned by the user usergroup group♪

Removing the archive in every treatment of the site is not the best idea. What's wrong with that? It would be better to set up a list of files in the archives in advance and then use it as a drawer for withdrawal. For example:#!/bin/sh TEMPLATES="/var/templates/archives" TEMPLATE=$(basename $1) tar -tvf "$1" | awk '{print $6}' >> "$TEMPLATES/$TEMPLATE.txt" This violin may be called after the arch/modification of the archive on the server. You can. crontab Specify bypass the catalogue of archives and the establishment/updating of templates, if required.

A simple crypt may be used to extract all parts of the archives:#/bin/bash path='./path/' # финальный слеш необходим list=$(ls $path*.tar.gz) for file in ls $path*.tar.gz.* do let i++ if [[ -f $(find $path*.tar.gz.$i) ]] then echo "file $path*.tar.gz.$i found." list="$list $path*.tar.gz.$i" else echo "file $path*.tar.gz.$i not found!" fi done cat $list > full.tar.gz tar zxf ./full.tar.gz -C $path rm -rf $list Write the way to the directory with the archive to the variable. path♪Make a file of the performing:chmod +x filename And let him in. The Archive will be unpacked in the same place as originally located, i.e. the director. pathDisclosure the last line to remove the archival source after the sale.

For example:$ find -maxdepth 1 -regex './\..*' | tar -cvzf archive.tar.gz -T - If it doesn't fit the prefix. ./ Before the names of the files/catalogons, it's a little longer:$ find -maxdepth 1 -regex './\..*' -printf '%P\n' | tar -cvzf archive.tar.gz -T - free -regex:$ find -maxdepth 1 -mindepth 1 -name .\* | tar -cvzf archive.tar.gz -T - $ find -maxdepth 1 -mindepth 1 -name .\* -printf '%P\n' | tar -cvzf archive.tar.gz -T - free find:$ tar -cvzf archive.tar.gz .??* but the mask will not be matched by files/cataloges with a name consisting of two symbols. .1.. then:$ tar -cvzf archive.tar.gz .[^.]*

man tar -k, --keep-old-files don't replace existing files when extracting,

If the file is in the cms file.Replacement$sitedir = 'E:/OpenServer/domains/cms/*'; ♪ $sitedir = '*'; archived with the caps.

Try adding -C After team:zip -C dirname.zip dirname/* Adjustment from the comment:Go inside the folder that needs to be packed, then pack all the files in it, and keep the director above:zip -r ../dirname.zip *

In this task, we will be able to use the magic of flows (standard streams) - to unpack gzip archive for the summer and repack it into bzip2 archive without creating an intermediate file on the disc. The team will look like this:gunzip < file.tar.gz | bzip2 > file.tar.bz2 If file.tar.gz You don't need any more repackage, you need to clear it with a separate team.For maximum (but less rapid) compression, substitute bzip2 write bzip2 -9♪

delete catalogues xxx♪ yyy and zzz Optical --exclude=шаблон:$ tar -cf файл.tar --exclude=xxx --exclude=yyy --exclude=zzz files but you can go the opposite way.If only catalogued files are required, where word is available testthat team can find them:$ find files/ -type f -path \*test\* and using the programme xargsto the archives:$ find files/ -type f -path \*test\* | xargs tar -cf файл.tar If the names of the files/catalogons can meet the SVS (e.g. gaps), then the challenge needs to be supplemented. find Opposition -print0♪ xargs - Ops -0:$ find files/ -type f -path \*test\* -print0 | xargs -0 tar -cf файл.tar If there is suspicion that the number of files multiplied along the length of the journey to them may exceed the maximum length of the team (see what is known about the limits of the programme) xargs♪ You can be a team ♪ :|xargs --show-limitsthat makes sense to replace the programme tar Opium -c (archived archive) -r (Appendix files to archives):$ find files/ -type f -path \*test\* -print0 | xargs -0 tar -rf файл.tar Example of the withdrawal of the request for a &quot; limit &quot; :$ :|xargs --show-limits Your environment variables take up 2510 bytes POSIX upper limit on argument length (this system): 2092594 POSIX smallest allowable upper limit on argument length (all systems): 4096 Maximum length of command we could actually use: 2090084 Size of command buffer we are actually using: 131072 The fourth line is just about the maximum length of the team.

man tar--overwrite--overwrite-dir-k, --keep-old-files http://white55.ru/tar.html Specify, sign off.

Hello.tar -cvjf newfile.tar.bz2 ./apache2 --exclude=./apache2/logs More in man tar.

Simple English man--check-links warn if number of hard links to the file on the filesystem mismatch the number of links recorded in the archive That means that the file other than the tar names in this file system have other names.The point is, at *nix, the data set (fail, caption, etc.) can have many true names (all equal). They're called hard links. Like this. new name may be added by the team ln♪ It is not possible to distinguish them on the first name (received by a systemic call open(s), mkdir(s), etc.).In addition, the name of the file is a reference (soft link). The links create a ln team with a key. -s♪

Just apply to the archives. https://php.net/manual/en/function.chmod.php ♪It is also possible to know these rights in advance. http://php.net/manual/en/function.fileperms.php and to transmit them chmod()♪

Utilization is recommended to be used to track both time and per cent to demonstrate https://habrahabr.ru/post/65384/ ♪ May be installed as follows apt-get install pv♪ Use, for example: # tar -cvf archive.tar * | pv -s $(du -sb | grep -o '[0-9]*') > out.tgz 81B 0:00:00 [1.54MB/s] [> ] 0%

It should work. tar -df archive.tar♪Young people's utilises don't usually pull anything out if they're successful, so if they don't find a difference, nothing will come out. If you don't like it, you'll be able to take advantage of the return value:tar -df ar.tar && echo No changes ♪ No changesif nothing changed. Such a trick works at Unix shell (e.g. bash), and as I just found out to my surprise, it's standard cmd.exe under Windows.

Use the exclusive option --exclude=PATTERN, but you've got a list of other things, I'd rather set up a list of what you need, not the other way around, for example, looking for what's right, and then the xargs and the tar itself.You'll find it again. find /path/to/dir -mmin -120 | xargs tar -cvf arhive.tar

It's not ssh or tar, it's unix-shell, which replaces * sets the names of the files in the current catalogue, and passes all of them. The starting point should be clearly indicated.tar -czvf archname.tar.gz * .??*(this will add the names of at least three symbols starting at point and length. If you write...*, there will be a catalogue added and... and that's not necessary.Either give the name of the catalogue, not the files on it:tar -czvf archname.tar.gz .In this case, the tar may try to add archname.tar.gz itself and make a mistake not to nervous him, place the archname in the parent catalogue:tar -czvf ../archname.tar.gz .

The exact meaning in some case could be. I think the files are being processed as a reference to them in the program's arguments, so you're gonna have to sort this list in advance.

Try this:cat *.tar.xz.** > all.tar.xztar -xJpf all.tar.xzThere's also a possibility of a convener.

According to the description, the check-links makes the following:If this option was given, tar will check the number of links dumped for each processed file. If this number does not match the total number of hard links for the file, a warning message will be output (6).When the tar is archiving, each rigid reference shall bear a block called the reference file. This is done to avoid duplicating the contents of the archives.Opation --check-links will issue a warning when the number of references to the file of the sealed seal does not match the number of references to the file in the file system. For example, if there is a file and there are strong references to it, a warning will be issued in the event that archiving this file and the file alone, as references will not be taken into account.