11-26-2008
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Please explain this command line ?
wc<infile<newfile
Thanx,
Saneesh Joseph. (2 Replies)
Discussion started by: saneeshjose
2 Replies
2. UNIX for Dummies Questions & Answers
Explain the output of the command “sort -rfn file1 | more” (1 Reply)
Discussion started by: wickbc
1 Replies
3. UNIX for Dummies Questions & Answers
Specifically what is the purpose of sed?
What is f?
Why is the 'cp f $phonefile' line needed when the script ‘goes live'?
Why might that two commands following sed be commented out at the present time ( i.e., during development)?
Thanks in... (2 Replies)
Discussion started by: knp808
2 Replies
4. Shell Programming and Scripting
find . -type f -ctime +3 -exec mv {} /somedirectory/ \;
in particular "-ctime v/s -mtime" and "difference between +3 and -3" (5 Replies)
Discussion started by: Rambo
5 Replies
5. Shell Programming and Scripting
I am using this line of perl code to change the file format and remove ^M at the end of each line in files:
perl -i -pe's/\r$//;' <name of file here>
Can you explain to me what this code does, and translate it into bash/awk/sed? (2 Replies)
Discussion started by: locoroco
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I saw this. But I don't know why we need this?
ls mydir > foo.txt ## I know what this will do, it will take the results and write to the file called foo.txt
ls mydir > foo.txt 2>&1 ## Don't know why we need 2>&1
Thanks. (2 Replies)
Discussion started by: samnyc
2 Replies
7. UNIX for Dummies Questions & Answers
Please explain grep -A 999999. I've seen this before, it always seems to be with six 9's as well. See an example below.
grep 'regexp' -A 999999 server.log | egrep -c 'Option=\' (6 Replies)
Discussion started by: scj2012
6 Replies
8. Red Hat
su - keibatch -c ""date ; /usr/local/kei/batch/apb/bin/JKEIKYK4140.sh -run "&$C$6&" WSUKE100201""
Not clear about : date ; /usr/local/kei/batch/apb/bin/JKEIKYK4140.sh -run "&$C$6&" WSUKE100201
Please help (2 Replies)
Discussion started by: honda_city
2 Replies
9. Shell Programming and Scripting
Hi Forum.
I have the following script /home/user/EDW_ENV.sh to setup some environment variables as:
##### section 1 PM_HOME #####
export PC_DIR_BASE=/data/informatica/ming
export DIR_ORACLE=/data/sw/apps/oracle/Oracle_scripts
export... (4 Replies)
Discussion started by: pchang
4 Replies
10. UNIX for Beginners Questions & Answers
I have a requirement to remove all non-ascii characters from a fixed length file. I used the below command which is removing special characters but somehow the total record length is being truncated to one space less. If it is a multi-byte string then many characters at the end are being truncated.... (8 Replies)
Discussion started by: eskay
8 Replies
DDB(8) BSD System Manager's Manual DDB(8)
NAME
ddb -- configure DDB kernel debugger properties
SYNOPSIS
ddb capture [-M -core] [-N -system] print
ddb capture [-M -core] [-N -system] status
ddb script scriptname
ddb script scriptname=script
ddb scripts
ddb unscript scriptname
ddb pathname
DESCRIPTION
The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily
via sysctl(8) MIB entries.
To ease configuration, commands can be put in a file which is processed using ddb as shown in the last synopsis line. An absolute pathname
must be used. The file will be read line by line and applied as arguments to the ddb utility. Whitespace at the beginning of lines will be
ignored as will lines where the first non-whitespace character is '#'.
OUTPUT CAPTURE
The ddb utility can be used to extract the contents of the ddb(4) output capture buffer of the current live kernel, or from the crash dump of
a kernel on disk. The following debugger commands are available from the command line:
capture [-M core] [-N system] print
Print the current contents of the ddb(4) output capture buffer.
capture [-M core] [-N system] status
Print the current status of the ddb(4) output capture buffer.
SCRIPTING
The ddb utility can be used to configure aspects of ddb(4) scripting from user space; scripting support is described in more detail in
ddb(4). Each of the debugger commands is available from the command line:
script scriptname
Print the script named scriptname.
script scriptname=script
Define a script named scriptname. As many scripts contain characters interpreted in special ways by the shell, it is advisable to
enclose script in quotes.
scripts
List currently defined scripts.
unscript scriptname
Delete the script named scriptname.
EXIT STATUS
The ddb utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
The following example defines a script that will execute when the kernel debugger is entered as a result of a break signal:
ddb script kdb.enter.break="show pcpu; bt"
The following example will delete the script:
ddb unscript kdb.enter.break
For further examples, see the ddb(4) and textdump(4) manual pages.
SEE ALSO
ddb(4), textdump(4), sysctl(8)
HISTORY
The ddb utility first appeared in FreeBSD 7.1.
AUTHORS
Robert N M Watson
BUGS
Ideally, ddb would not exist, as all pertinent aspects of ddb(4) could be configured directly via sysctl(8).
BSD
December 24, 2008 BSD