05-22-2002
There are a few problems here. First -atime is access time. You want -mtime which is modification time. Next the +0 is going to exclude all the files you want and pick up the rest. "find /home/bob -mtime -1" will give you alist of files modified less than a day ago. But you will also get directories as well as files. "-type f" will take care of that. And finally, you don't want a seperate run of tar for each file...you want to run tar just once.
tar cvf /home/bob/files.tar `find /home/bob -mtime -1 -type f`
will do it. But this assumes that you have enought space on your command line to handle all of the files in question. If you "cd /home/bob" first and use "." instead of "/home/bob" in the find command, you will shorten the length of the list and defer the problem. And having the output file in your home directory is dangerous. If you remove yesterday's before you run the new command you should be ok. But if files.tar gets added to the list, you're in trouble. Putting it in /tmp or /var/tmp while the command is running might be safer.
So my final answer...
cd /home/bob
tar cvf /var/tmp/files.tar `find . -mtime -1 -type f`
mv /var/tmp/files.tar .
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am creating a disaster recovery plan for my Linux 7.2 machine. I have two backups from my current machine.
One created using the command
tar -cvpf /dev/st0 --exclude=/proc --directory / .
and one created with the command
find / /boot /home -mount -path '/proc' -prune -o -print |... (4 Replies)
Discussion started by: jeremiebarber
4 Replies
2. UNIX for Dummies Questions & Answers
When I am doing the first command the result shows all the files, links, directories except the ones that contain the word logs
find . -type f -o -type l -o -type d | grep -v logs
But when I am trying to do this even the logs are getting tarred
tar -cvf fdtvision.tar `find . -type f -o -type l... (2 Replies)
Discussion started by: venu_nbk
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I've got dozens of tar's with two files in each one,
live_access_log & live_error_log (one tar for each day, backups).
The probelm is i need to match a pattern in all of the archive_access_log files and output the line to a seperate file (All_access.log).
I.e. I need to get details... (21 Replies)
Discussion started by: tom123
21 Replies
4. Shell Programming and Scripting
The below tar command works fine for me,
tar -cvf - `find ./srcdir -type d` | (cd ./destdir ; tar -xvf - )
but this version is giving error to me:
cd ./srcdir &&
tar -cf - . |
gzip -9 |
cd ../destdir &&
gzip -d |
tar -xf -
error is: gzip: compressed data not read from a terminal.... (2 Replies)
Discussion started by: royalibrahim
2 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
4 files are returned when i issue 'find . -mtime -1 -type f -ls'.
./ora_475244.aud
./ora_671958.aud
./ora_934052.aud
./ora_934050.aud
However, when I issued the below command:
tar -cvf test.tar `find . -mtime -1 -type f`, the tar file only contains the 1st file -... (2 Replies)
Discussion started by: ahSher
2 Replies
6. UNIX for Advanced & Expert Users
I've some problem concerning tar command.
Sometime tar command submitted to create a tar file, in execution loop over the same group of files.
Can anyone help me?
Tanks (15 Replies)
Discussion started by: Jocker
15 Replies
7. Shell Programming and Scripting
find . -type f -name "*.sql" -print|xargs perl -i -pe 's/pattern/replaced/g'
this is simple logic to find and replace in multiple files & folders
Hope this helps.
Thanks
Zaheer (0 Replies)
Discussion started by: Zaheer.mic
0 Replies
8. Shell Programming and Scripting
Hello people!
I would like to create one script following this stage
I have one directory with 100 files
File001
File002
...
File100
(This is the format of content of the 100 files)
2012/03/10 12:56:50:221875936 1292800448912 12345 0x00 0x04 0
then I have one... (0 Replies)
Discussion started by: Abv_mx81
0 Replies
9. UNIX for Advanced & Expert Users
Hello All i have a KSH script which basically takes attribute name as input argument and searches whole Netezza appliance and prints information of where that column is used (Table/Views) etc.
Problem with this approach business users have to raise SUDO access request, Install Putty, run through... (1 Reply)
Discussion started by: Ariean
1 Replies
chroot(1M) System Administration Commands chroot(1M)
NAME
chroot - change root directory for a command
SYNOPSIS
/usr/sbin/chroot newroot command
DESCRIPTION
The chroot utility causes command to be executed relative to newroot. The meaning of any initial slashes (/) in the path names is changed
to newroot for command and any of its child processes. Upon execution, the initial working directory is newroot.
Notice that redirecting the output of command to a file,
chroot newroot command >x
will create the file x relative to the original root of command, not the new one.
The new root path name is always relative to the current root. Even if a chroot is currently in effect, the newroot argument is relative to
the current root of the running process.
This command can be run only by the super-user.
RETURN VALUES
The exit status of chroot is the return value of command.
EXAMPLES
Example 1: Using the chroot Utility
The chroot utility provides an easy way to extract tar files (see tar(1)) written with absolute filenames to a different location. It is
necessary to copy the shared libraries used by tar (see ldd(1)) to the newroot filesystem.
example# mkdir /tmp/lib; cd /lib
example# cp ld.so.1 libc.so.1 libcmd.so.1 libdl.so.1 libsec.so.1 /tmp/lib
example# cp /usr/bin/tar /tmp
example# dd if=/dev/rmt/0 | chroot /tmp tar xvf -
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
cd(1), tar(1), chroot(2), ttyname(3C), attributes(5)
NOTES
Exercise extreme caution when referencing device files in the new root file system.
References by routines such as ttyname(3C) to stdin, stdout, and stderr will find that the device associated with the file descriptor is
unknown after chroot is run.
SunOS 5.10 15 Dec 2003 chroot(1M)