CPIO weird thing

CPIO weird thing

Post by Adam Walke » Thu, 15 Oct 1998 04:00:00



When I am doing a system wide CPIO in the evenings I wrote a script
to log the events and then do a echo $? to check the status of the
backup.
Ok well the script works great, BUT the echo $? always responds with
a 2 because cpio ends with 'not able to get information on .'
Any help is appreciated, I am using cpio with the ovcB flags.

here is the output (end of log file, end of backuplog):
===
Backup Started at   Tue Oct 13 23:00:02 PDT 1998
Backup Ended at     Tue Oct 13 23:52:02 PDT 1998
                Backup status = 2
$ tail backuplog.1
/config.done
/smit.script.may19.Z
/agamatmp/dist1.tar.Z
/agamatmp
/mbox
/smit.log.may19.Z
cpio: 0511-025 Cannot get information about .
4189380 blocks
Backup Ended at     Tue Oct 13 23:52:02 PDT 1998
===

Thanks in advance,

Adam Walker

 
 
 

CPIO weird thing

Post by Jim Mellande » Thu, 15 Oct 1998 04:00:00



> When I am doing a system wide CPIO in the evenings I wrote a script
> to log the events and then do a echo $? to check the status of the
> backup.
> Ok well the script works great, BUT the echo $? always responds with
> a 2 because cpio ends with 'not able to get information on .'
> Any help is appreciated, I am using cpio with the ovcB flags.

<snip>

Yeah, cpio generates an error if any files are missing, which can be
annoying.  What I do is pipe the output of cpio thru dd & check the
status of the dd command, like this:

find . -print|cpio -oacv|dd bs=5120 of=/dev/rmt0 2>&1
status=$?

Incidentally, its usually a good idea to specify the 'a' flag to cpio,
so that the files accessed keep their original timestamp.

 
 
 

1. Weird Ping, weird FTP, weird Telnet... HELP!!!

Can anyone diagnose this for me?

I'm in the process of building up a firewall but at some stage I musta
messed up and am now getting really weird results.

This is the results of a ping from 192.168.0.1 to 192.168.0.1 (the box
which will become the fireawall).

# PING 192.168.0.1
PING 192.168.0.1 (192.168.0.1) from 192.168.0.1 : 56(84) bytes of
data.
64 bytes from 192.168.0.1: icmp_seq=0 ttl=225 time=0.7ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=225 time=80001.0ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=225 time=160000.9ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=225 time=240000.8ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=225 time=320000.8ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=225 time=400000.7ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=225 time=480000.7ms

^c

--- 192.168.0.1 ping statistics ---
509 packets transmitted, 8 packets received, 98% packet loss
round-trip min/avg/max = 0.7/280000.7/560000.6 ms

This also happens when I do it from other machines behind the firewall
but I was very surprised when it did it when pinging itself.

Theres a pattern of 80000ms increments between successful pings...
Can't figure out whats wrong though.

If I try to telnet or FTP, I have to wait for an eternity b4 the login
prompt appears after the initial "connected" msg. But once I login
there is no problem using the console or transferring files. Same
thing for other machines to 192.168.0.1. So the network is "working"
but its waiting for something.

Has anyone had this happen to them b4 and manage to solve it?

Any help appreciated

Regards,

2. ? about building kernel

3. Weird, weird, weird issue ....

4. Q: yppasswd protocol

5. (newbie) weird thing with linux applications

6. package tcp_wrappers wont work

7. weird csh thing

8. Screnn Shell, ASCII and Binary Editors under X!!!!

9. weird ant things

10. XV does -weird- things

11. Weird Thing: sb module hangs every 2nd boot?

12. weird qconfig thing

13. Weird things in csh (and kernel?)