08-22-2012
script & issues with non-AIX commands
I need to capture lengthy screen puts and direct to .txt.
HTML Code:
Script command is started on Wed Aug 22 13:27:36 EDT 2012.
# qcp
sh: qcp: not found.
An issue I have is that script command doesn't take non-AIX commands.
I need to run application-specific commands and capture the output in .txt.
Please advise.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, I need help again. When I run this shell script, it only runs the unld_date.sql piece and exits. How can I structure this to run all the way to the end? When I don't have the unld_date.sql piece in here, everything runs fine from the date compare piece all the way to the end. Thanks in... (5 Replies)
Discussion started by: siog
5 Replies
2. Shell Programming and Scripting
Here is my script
#!/bin/bash
pwd
cd /var/lib/pgsql
Both "pwd" and "cd" are not executed is there any other way i can change the current working directory to /var/lib/pgsql pls help! (9 Replies)
Discussion started by: perk_bud
9 Replies
3. Shell Programming and Scripting
Hi All,
I am trying to write a script to get the user information & the command executed.
I tried something like this :
w | sort | awk '{print$5$6$7}'
My requirement is to identify the users who execute the same command at same time.
I need the user name & the... (2 Replies)
Discussion started by: vijayarajvp
2 Replies
4. Shell Programming and Scripting
Hi all,
I've been pulling my hair out with this problem for 3 days:wall: now without success any help would be massively appreciated.
Basically the script is used to shutdown a rails server so a new IP address can be assigned, the shutdown part is taken care of in function_one using the... (2 Replies)
Discussion started by: danmc
2 Replies
5. UNIX for Dummies Questions & Answers
AIX & DB2 paging issues
Hello I needs some help on AIX & DB2 paging issues. Recently a db2 query caused paging issues which then lead to memory problems and a server restart. Is there anyway of finding out what db2 queries were causing the problem..
Thanks in advance (2 Replies)
Discussion started by: nedkao
2 Replies
6. AIX
I am trying to use this command to eject the tape
mt -f /dev/rmt/0 unload
but it gives me error
mt -f /dev/rmt/0 unload
mt: 0511-575 unload is not a recognized subcommand.
Usage: mt Subcommand
Valid subcommands are:
weof
eof
fsf
bsf
... (5 Replies)
Discussion started by: filosophizer
5 Replies
7. Red Hat
Hi All,
The scripts developed in AIX can be executed in Red Hat Linux too? Because, we are migrating OS from AIX to LINUX.
Will there be any differences in commands?
Thanks in advance!!!
Regards,
U (2 Replies)
Discussion started by: unme
2 Replies
8. Shell Programming and Scripting
Hi,
I am migrating few of the shell scripts from existing SUN Solaries to AIX.
My script contains some command like 'dos2unix' and 'unix2dos' which are not compatible in AIX flavour. Please let me know if there is any such commands in AIX which can replace these commands.
Thanks. (1 Reply)
Discussion started by: 46019
1 Replies
9. UNIX and Linux Applications
Hi Team,
I am facing issue while using Xalan & Xerces for my application.
Below are my environment details i am using :-
Platform:- Oracle Linux 6.6
Compiler :- solarisstudio12.3 C++ compiler for Linux
Below are the versions of Xalan & Xerces source code used to build the shared object... (0 Replies)
Discussion started by: agrachirag
0 Replies
10. UNIX for Beginners Questions & Answers
I am new in scripting,
I need script(BASH) which do telenet to one of the elements & run few commands , after running it successfully it will check status of files & exit.
Help is greatly appreciated 🙏 (2 Replies)
Discussion started by: Vinesh_123
2 Replies
TEXTDUMP(4) BSD Kernel Interfaces Manual TEXTDUMP(4)
NAME
textdump -- textdump kernel dumping facility
SYNOPSIS
options KDB
options DDB
DESCRIPTION
The textdump facility allows the capture of kernel debugging information to disk in a human-readable rather than the machine-readable form
normally used with kernel memory dumps and minidumps. This representation, while less complete in that it does not capture full kernel
state, can provide debugging information in a more compact, portable, and persistent form than a traditional dump. By combining textdump
with other ddb(4) facilities, such as scripting and output capture, detailed bug information can be captured in a fully automated manner.
FORMAT
textdump data is stored in a dump partition in the same style as a regular memory dump, and will be automatically extracted by savecore(8) if
present on boot.
textdump files are stored in the tar(5) format, and consist of one or more text files, each storing a particular type of debugging output.
The following parts may be present:
ddb.txt Captured ddb(4) output, if the capture facility has been used. May be disabled by clearing the debug.ddb.textdump.do_ddb
sysctl.
config.txt Kernel configuration, if has been compiled into the kernel. May be disabled by clearing the debug.ddb.textdump.do_config
sysctl.
msgbuf.txt Kernel message buffer, including recent console output if the capture facility has been used. May be disabled by clearing the
debug.ddb.textdump.do_msgbuf sysctl.
panic.txt Kernel panic string, if the kernel panicked before the dump was generated. May be disabled by clearing the
debug.ddb.textdump.do_panic sysctl.
version.txt Kernel version string. My be disabled by clearing the debug.ddb.textdump.do_version sysctl.
Kernel textdumps may be extracted using tar(1).
CONFIGURATION
The textdump facility is enabled as part of the kernel debugger using options KDB and options DDB. By default, kernel dumps generated on
panic or via explicit requests for a dump will be regular memory dumps; however, by using the textdump set command in ddb(4), or by setting
the debug.ddb.textdump.pending sysctl to 1 using sysctl(8), it is possible to request that the next dump be a textdump.
If at the ddb(4) command line, the commands textdump set, textdump status, and textdump unset may be used to set, query, and clear the
textdump pending flag.
As with regular kernel dumps, a dump partition must be automatically or manually configured using dumpon(8).
EXAMPLES
In the following example, the script kdb.enter.panic will run when the kernel debugger is entered as a result of a panic, enable output cap-
ture, dump several useful pieces of debugging information, and then invoke panic in order to force a kernel dump to be written out followed
by a reboot:
script kdb.enter.panic=textdump set; capture on; show allpcpu; bt;
ps; alltrace; show alllock; call doadump; reset
In the following example, the script kdb.enter.witness will run when the kernel debugger is entered as a result of a witness violation,
printing lock-related information for the user:
script kdb.enter.witness=show locks
These scripts may also be configured using the ddb(8) utility.
SEE ALSO
tar(1), ddb(4), tar(5), ddb(8), dumpon(8), savecore(8), sysctl(8)
HISTORY
The textdump facility first appeared in FreeBSD 7.1.
AUTHORS
The textdump facility was created by Robert N. M. Watson.
BSD
December 24, 2008 BSD