Application behaving in 3 different ways on 3 different machines Post: 302752661

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

ftp application behaving erratically

Hi, I am working on a custom made FTP application. The application is behaving erratically for the "ls" command. Wild card character passed to the "ls" command (like "ls *temp") is giving inconsistent results. On debuggin I have found that the "ls" command is implemented as shown below in the...

2. UNIX for Advanced & Expert Users

csplit not behaving

I have a large file with the first 2 characters of each line determining the type of record. type 03 being a subheader and then it will have multiple 04 records. eg: 03,xxx,xxxx,xxxx 04,xxxxxxxxxxxxxxxxxxxxxxxxxxxx 04,xxxxxxxxxxxxxxxxxxxxxxxxxxxx 03,xxx,xxx,xxx ...

3. Red Hat

application to be run on machines connected in same network

I have a set up of 5 machines which are connected in same network. Now i want to run a small application so that those machines are not ideal.

4. Shell Programming and Scripting

tr command behaving unexpectedly

Im trying to execute the below command on our server to list files and replace the newline in the file list with spaces, but the character 'n' is getting replaced with a space, is there any environment variable that needs to be set in UNIX? sh -c 'ls -trx...

5. UNIX for Advanced & Expert Users

FTP behaving erraneous way

Hi Gurus, I tried FTP one file to UNIX which got values like wel^come If I see the content in unix, it shows like wel^Zcome ^ coverted into ^Z (Control + Z ) Can someone please share what is happening here? Thanks, Shahnaz

6. Red Hat

nslookup behaving strangely

I have two servers on same domain. one can nslookup other cannot Psu100 can lookup to psu000, psu010 & psu011 Psu110 can NOT lookup to psu000, psu010 & psu011 I verified resolv.conf entries on both psu000 and psu010 and it contains both name servers (10.200.10.21 & 10.200.11.22).I am...

7. UNIX and Linux Applications

Linux application upgrade ways

Hello. I need upgrade memcached. This software is installed throuth yum. In official repositories isn`t newest version of memcached, but this one is vulnerable. So looks like I need built it from source, but I dont really want to install c libraries un compilers on system. 1.) So can I compile...

8. Shell Programming and Scripting

awk not behaving as expected

Hi, Immediate help on below will be appreciated. I have to read a file (max of 10MB) which will have no new line characters, i.e. data in single line. and have to inster '\n' at every 100 characters. and if record starts with 'BUCA' then need to pick value of length 10 at position 71 and...

9. UNIX for Advanced & Expert Users

[Solved] wc behaving weirdly

Can anyone explain why wc is behaving weirdly? Their are only 2 occurrences but wc thinks their are 7 occurrences. I have even manually checked this. $ grep -i base * lit: base xx lit.lst:003- 00103 BASE XX $ grep -i base * | wc -w ...

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)