09-04-2015
Quote:
So, that only means the file is not copied correctly. Isn't it your intention anyway. Findout if the file copied is the same or corrupt ?. Does it not solve your issue?.
Yes that does - but do I keep that as the bench mark to check if the file is corrupted or not ..
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
This is my worst nightmare in recent years!!!
I spent two days writing a proposal due tomorrow, ftp'ed the Word doc to a Unix machine in ASCII mode (i forgot to turn BIN on). Then I was trying to help a colleague download it and I accidently download the ASCII file back to the same dir on my... (1 Reply)
Discussion started by: venkir
1 Replies
2. UNIX for Dummies Questions & Answers
HI
I need to validate a file in UNIX to contain only ascii characters.This is a production issue.Can anyone help with the command?
Thanks
Subbarao (1 Reply)
Discussion started by: srichakra9
1 Replies
3. Shell Programming and Scripting
Hello,
How to i determine via ftp commandline if files on ftp server is ascii or binary files. Like every other comon windows ftp program does it automatically.
regards
Thomas (5 Replies)
Discussion started by: congo
5 Replies
4. UNIX for Advanced & Expert Users
Hi,
I am having unix script that passes argument value to script. The script finds the file and keeps it in a directory.
I need to ftp this file to another server. Please guide me how to acieve this.
I am able to connect to ftp server but i am not able to use the unix argument in the ftp... (0 Replies)
Discussion started by: pyaranoid
0 Replies
5. Shell Programming and Scripting
Hi,
I want to compare the size of the files in my local machine before ftp ing it and the size of the file in the remote machine i.e after ftping . SO that the ftp is successful . (3 Replies)
Discussion started by: dineshr85
3 Replies
6. Shell Programming and Scripting
hi
i am receiving a file from one system , i have to verify the format of the file data i.e whether the data is in acii format or binary format,
please help
thanks in advance
satya (1 Reply)
Discussion started by: Satyak
1 Replies
7. Shell Programming and Scripting
Hi,
is there a way to check if the initial few characters are ebcdic or ascii in a file? (1 Reply)
Discussion started by: ahmedwaseem2000
1 Replies
8. Solaris
The system is a SunFire V440 running SunOS 5.10
About once every 3-4 weeks, the system will reboot into single user mode on its own, and then I run svcs -xv, the filesystem service and dependent services will be disabled due to the metadisk file system being corrupted.
The I've been doing... (2 Replies)
Discussion started by: the.gooch
2 Replies
9. Shell Programming and Scripting
Hi,
I need to have a shell script that FTP's a zipped file from a particular location.
I have some path and inside that path i will have folders like x_timestamp and inside x_timestamp there may many folders based upon events like y_111,y_222,y_333.Inside each event there will be another... (3 Replies)
Discussion started by: weknowd
3 Replies
10. UNIX for Beginners Questions & Answers
So, i have this requirement where i need to check the file format, whether it's EBCDIC or ASCII, and based on format retrieve the information from that file:
my file is:
file1.txt-->this ebcdic file
file2.txt-->ascii file
i tried below code:
file=file1.txt
type="`file $file`"
i get... (7 Replies)
Discussion started by: gnnsprapa
7 Replies
LEARN ABOUT OSF1
expand_dump
expand_dump(8) System Manager's Manual expand_dump(8)
NAME
expand_dump - Produces a non-compressed kernel crash dump file
SYNOPSIS
/usr/sbin/expand_dump input-file output-file
DESCRIPTION
By default, kernel crash dump files (vmzcore.#) are compressed during the crash dump. Compressed core files can be examined by the latest
versions of debugging tools that have been recompiled to support compressed crash dump files. However, not all debugging tools may be
upgraded on a given system, or you may want to examine a crash dump from a remote system using an older version of a tool. The expand_dump
utility produces a file that can be read by tools that have not been upgraded to support compressed crash dump files. This non-compressed
version can also be read by any upgraded tool.
This utility can only be used with compressed crash dump files, and does not support any other form of compressed file. You cannot use
other decompression tools such as compress, gzip, or zip on a compressed crash dump file.
Note that the non-compressed file will require significantly more disk storage space as it is possible to achieve compression ratios of up
to 60:1. Check the available disk space before running expand_dump and estimate the size of the non-compressed file as follows: Run tests
by halting your system and forcing a crash as described in the Kernel Debugging manual. Use an upgraded debugger to determine the value of
the variable dumpsize. Multiply this vale by the 8Kb page size to approximate the required disk space of the non-compressed crash-dump.
Run expand_dump and pipe the output file to /dev/null, noting the size of the file that is printed when expand_dump completes its task.
RETURN VALUES
Successful completion of the decompression. The user did not supply the correct number of command line arguments. The input file could
not be read. The input file is not a compressed dump, or is corrupted. The output file could not be created or opened for writing and
truncated. There was some problem writing to the output file (probably a full disk). The input file is not formated consistantly. It is
probably corrupted. The input file could not be correctly decompressed. It is probably corrupted.
EXAMPLES
expand_dump vmzcore.4 vmcore.4
SEE ALSO
Commands: dbx(1), kdbx(8), ladebug(1), savecore(8)
Kernel Debugging
System Administration
expand_dump(8)