08-28-2001
My problem is the same....
!$ tar -cvf /dev/st0 test1.txt
test1.txt
!$ tar -rvf /dev/st0 test2.txt
test2.txt
!$ tar -tvf /dev/st0
only display test1.txt
And I need that display...
!$ tar -tvf /dev/st0
test1.txt
test2.txt
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hi ,
On AIX 4.3.3
I typed the following command
tar -cvf <filename> ( actually I forgot to type the device name)
the output was change in the file size to 10240 bytes
I tried tar -xvf to extract the same but file size is same.
The file was "txt" file and was readable before the... (2 Replies)
Discussion started by: amit
2 Replies
2. UNIX for Advanced & Expert Users
Can someone please verify for me if tar compresses the directory or filesystem it is asked to back up??
reason am asking is I checked the size of the /home directory before running a tar command
now, after I ran the tar command and the tar was done extracting the directory from the archive, I... (2 Replies)
Discussion started by: TRUEST
2 Replies
3. UNIX for Advanced & Expert Users
I am using a tar command to backup my system. It works properly.
I have had some trouble and I need to restore a few files.
I am using the following command :
tar xvf /dev/rmt2h myfile_to_restore
The tar command seemd to work but after a long time I got the following error message :... (6 Replies)
Discussion started by: renard
6 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
I've done a tar -cvf data.tar *
in our live data directory on a Solaris machine.
I copy the tar file to the test area and try
tar -xvf data.tar .
and it uses the full path in the tar file and overwrites the live ones again.
I've used tar many a time and don't understand why its happening.... (1 Reply)
Discussion started by: kinhell
1 Replies
6. Shell Programming and Scripting
i have some 685 files in my directory.Below the count:
find . -name "CurrentCollectorMeterReadBackup_2009*" -exec ls -ltr {} \; | wc -l
685
i want to tar them but it is telling me arg list too long. how to tar all this files in one shot
tar -cvf - -L... (1 Reply)
Discussion started by: ali560045
1 Replies
7. 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
8. Linux
can someone help me here. apparently, the colon i included in the name of this file is making it difficult for tar to untar it. please help
####### tar xvf DailyConfigs_Nov-19-11\:00-2009.tar
rsh: DailyConfigs_Nov-19-11: Name or service not known
tar: DailyConfigs_Nov-19-11\:00-2009.tar:... (4 Replies)
Discussion started by: SkySmart
4 Replies
9. Ubuntu
Hello everyone, I´ve got a problem when I try to untar a file.
The following errors appear:
tar: Skipping to next header
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
Can anyone help me? Thanks in advance! (1 Reply)
Discussion started by: katkat
1 Replies
10. Shell Programming and Scripting
Hi all,
I have a tar file and inside that tar file is a folder with additional tar.gz files. What I want to do is look inside the first tar file and then find the second tar file I'm looking for, look inside that tar.gz file to find a certain directory. I'm encountering issues by trying to... (1 Reply)
Discussion started by: bashnewbee
1 Replies
WDMD(8) System Manager's Manual WDMD(8)
NAME
wdmd - watchdog multiplexing daemon
SYNOPSIS
wdmd [OPTIONS]
DESCRIPTION
This daemon opens /dev/watchdog and allows multiple independent sources to detmermine whether each KEEPALIVE is done. Every test interval
(10 seconds), the daemon tests each source. If any test fails, the KEEPALIVE is not done. In a standard configuration, the watchdog timer
will reset the system if no KEEPALIVE is done for 60 seconds ("fire timeout"). This means that if a single test fails 5-6 times in row,
the watchdog will fire and reset the system. With multiple test sources, fewer separate failures back to back can also cause a reset, e.g.
T seconds, P pass, F fail
T00: test1 P, test2 P, test3 P: KEEPALIVE done
T10: test1 F, test2 F, test3 P: KEEPALIVE skipped
T20: test1 F, test2 P, test3 P: KEEPALIVE skipped
T30: test1 P, test2 F, test3 P: KEEPALIVE skipped
T40: test1 P, test2 P, test3 F: KEEPALIVE skipped
T50: test1 F, test2 F, test3 P: KEEPALIVE skipped
T60: test1 P, test2 F, test3 P: KEEPALIVE skipped
T60: watchdog fires, system resets
(Depending on timings, the system may be reset sometime shortly before T60, and the tests at T60 would not be run.)
A crucial aspect to the design and function of wdmd is that if any single source does not pass tests for the fire timeout, the watchdog is
guaranteed to fire, regardless of whether other sources on the system have passed or failed. A spurious reset due to the combined effects
of multiple failing tests as shown above, is an accepted side effect.
The wdmd init script will load the softdog module if no other watchdog module has been loaded.
wdmd cannot be used on the system with any other program that needs to open /dev/watchdog, e.g. watchdog(8).
Test Source: clients
Using libwdmd, programs connect to wdmd via a unix socket, and send regular messages to wdmd to update an expiry time for their connection.
Every test interval, wdmd will check if the expiry time for a connection has been reached. If so, the test for that client fails.
Test Source: scripts
wdmd will run scripts from a designated directory every test interval. If a script exits with 0, the test is considered a success, other-
wise a failure. If a script does not exit by the end of the test interval, it is considered a failure.
OPTIONS
--version, -V
Print version.
--help, -h
Print usage.
--dump, -d
Print debug information from the daemon.
--probe, -p
Print path of functional watchdog device. Exit code 0 indicates a
functional device was found. Exit code 1 indicates a functional device
was not found.
-D
Enable debugging to stderr and don't fork.
-H 0|1
Enable (1) or disable (0) high priority features such as realtime
scheduling priority and mlockall.
-G name
Group ownership for the socket.
-S 0|1
Enable (1) or disable (0) script tests.
-s path
Path to scripts dir.
-k num
Kill unfinished scripts after num seconds.
-w path
The path to the watchdog device to try first.
2011-08-01 WDMD(8)