very bizzare file writing problem Post: 302262384

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Bizzare (while statement)

I'm trying to use the while statement to increment a positive number, with a leading "0". when I pass it through, it seems to come out with a negative value, and all the increments remain negative. This is what I have: i=010986294184 j=010986988888 while ; do echo $i i=(($i + 1)) done...

2. UNIX for Dummies Questions & Answers

Problem writing file path to txt file

if test -z "$1" then echo "you must give a filename or filepath" else path=`dirname $1` f_name =`basename $1` if path="." then path=`pwd` fi fi cat $f_name $path >> index.txt The only problem I am encountering with this is writing $path to index.txt Keeps going gaga: cat:...

3. UNIX for Advanced & Expert Users

Problem while writing to a file...?

Hi, I have an issue with the file writing... It is, Suppose that if I am writing some data to a file... and at the same time another user has opened the file and want to write in to the file(writing to the file at the same time)...the another has to know that someone has opened the file, mean...

4. Shell Programming and Scripting

Problem in writing the data to a file in one row

5. IP Networking

Bizzare network attack?

A server I host is having very rare glitches where a file the user downloads will have incorrect contents. This almost never happens when I am looking, I caught it once and only once -- a user messaged me saying his antivirus had given him a warning about an image file downloaded from his...

6. Shell Programming and Scripting

help with counting processes, bizzare behavior

I have a ksh script (dtksh Version M-12/28/93d on Solaris 10) that is run daily by cron and sometime hangs forever. I need to detect if there is an old copy hung before I start the new run, and if so send an email and exit the script. Here is part of the code: #!/usr/dt/bin/dtksh...

7. UNIX for Advanced & Expert Users

Bizzare TCP/IP problem

Hi all. I have a really really weird problem that I've been working on for days. The problem manifested as users cannot connect to our web servers via SSH when they're using our wireless network. Here's where it gets weird: - Clients from anywhere other than the wireless subnet can...

8. Programming

Bizzare optimization problem

I have a C program that, for the life of me, I can't see any possible stack corruption in but for some reason corrupts a local variable to 0 when not referenced. My compiler is gcc 4.3.4. But my question's not really a code question, it's a compiler question. The glitch is weirdly specific: ...

9. Shell Programming and Scripting

Problem with writing into a file through shell script

Hi all, I have a shell script which I use to login to the server from the client and then from the server I run a bunch of other scripts to complete my task. I am having problems with the script below- #!/bin/bash while read line do connections=`echo $line | cut -d " " -f 1` period=`echo...

10. Shell Programming and Scripting

Bizzare behavior on redirect of stdout

Oracle Linux 5.6 64-bit (derivative of RHEL) Dear Ann Landers, This is about as bizarre as anything I've ever seen. I have a little test script I've been working with. When I redirect stdout to a file, no file. Make a copy of the script to another name. Execute it and redirect stdout, and...

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)