30 20 ** 2 tar –cz /home/user1 > /home/user1/backup.tar.gz
Is it alright ?
Sigh...
RudiC has told you two times now to separate the two asterisks by a space. The line as you present it is still wrong because of that and no matter what options to tar you try will change anything about that BECAUSE THIS IS NOT THE PROBLEM IN FIRST PLACE!
Try a layered approach: first, consult the man pages of cron and learn how to configure a (any) command to be run by cron. Only then concern yourself with constructing the correct tar-command: first manually. When it finally does what you want it to do put it into cron using your new-found expertise on creating cron-jobs.
So much as a starter: cron jobs have NOT the same environment as commands run from an interactive session, namely the PATH variable is empty and therefore you should use full pathnames. instead of tar <cmd> /some/path you need to write something like /usr/bin/tar <cmd> /some/path. Notice the full path to the command. Your path might differ, but you can easily get the (on your system) correct path with the which command:
Is there a way I can check if a file is comppressed or not? (Be it tar/gzip or compress). trying to write a generic housekeeping scrit that will delete files over 6 months old and compress any uncompressed files if less than 6 months old. But not sure if there is a clever way to check except for... (4 Replies)
Are any of you guys aware of any problems when trying to sort compressed fields? Why I uncompress the file I am trying to sort, I have no problem sorting but when I try to sort compressed fields it doesnt work properly. I need to be able to sort these compressed fields. Any explanation why? (1 Reply)
Hi,
I have a file that has got compressed data. I would want to uncompress the packed decimal data(not the file). is there a way to do that in ksh? (6 Replies)
Hi
i have a filename.tar.bz2 and i have to parse it with a tool that doesn't support compressed files.
I have to do it for many big files, so i can't decompress and then process. I'd like to do something like:
tar -jxvf namefile.tar.bz2 | parsing_tool
i mean analyze it directly,... (4 Replies)
Hello all
I want to help
I have some compressed files on the system
When you want to unzip these files
Delete any file which symlink
"ln -s"
{{
I need script is necessary
Script contain:
Any operation to decompress the system is doing to delete any symlink... (0 Replies)
i have a file 4d7a94d0.bbb.1292
when i do
file 4d7a94d0.bbb.1292
the ouput is below
4d7a94d0.bbb.1292: gzip compressed data - deflate method
and i run this command
gunzip -c 4d7a94d0.bbb.1292 | awk '{gsub("\"","")}/I_ACCOUNT_ID/{print $2}' RS=":|;" FS=","
i get... (3 Replies)
I need UNIX scripts for polling, Uncompressing files and moving files between directory. Also trying to save file paths and any other variables in an independent file (.env) and use these at runtime by executing this file in the main script. (3 Replies)
Hi All,
Is there is any way to find the size of compressed file without doing decompression. The size should give the original uncompressed data size
Thanks
Arun (3 Replies)
Discussion started by: arunkumar_mca
3 Replies
LEARN ABOUT SUNOS
chroot
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)