05-02-2009
Quote:
Originally Posted by
edfair
BTW, the heading for SCO still implies the name of the Santa Cruz Operation, parts of which (the unix parts) were purchased by Caldera, then renamed The SCO Group. TSCOG is still in operation, but in chapter 11, and probably is going to be forced into chapter 7 and liquidation.
No it does not imply anything. The description says:
Quote:
Santa Cruz Operation (SCO) was a software company based in Santa Cruz, California which was best known for selling three UNIX variants for Intel x86.
Was means "in the past" and clearly does not imply anything about now.
6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Here's a fun one...
What's the best way to script looking for a process when it runs? For example, what if a process is running that's been set up graphically, which you would like the entire command line string for? Say it's rpm for the sake of having a command to use as an example. You want... (2 Replies)
Discussion started by: sysera
2 Replies
2. HP-UX
Hi
I have a doubt regarding process states in HP unix system. Is there a way to check whether a process is hanged or still actively running? I have few scripts which run for a long time. but sometimes these are getting hanged. But i'm never sure whether they are running or waiting in kind of... (4 Replies)
Discussion started by: truth
4 Replies
3. AIX
Hi,
Is there any command that I can issue to check who is actively using my harddisk? I notice that yesterday the hdisk0 and hdisk1 is really actively being used and is reaching almost 100%. I realized that this is because of paging which is climbing up to 70%.
However, just this morning... (3 Replies)
Discussion started by: depam
3 Replies
4. AIX
Dear all,
I am faced with an error "UX ER087-0" failling to connect to the server.
Any ideas of what might be causing the error?
Many thanks (17 Replies)
Discussion started by: captain.scorpio
17 Replies
5. Shell Programming and Scripting
ok, here's the scoop, google has similar, but nothing that quite fits the bill. here is what I'm up against:
i have a linux system that is running both kde 3.x and gnome 2.x, selectable via gdm.
the kde 3.x app menu is heavily modified and i'm looking for a way to import that over to the... (0 Replies)
Discussion started by: macphail
0 Replies
6. What is on Your Mind?
Hello All,
Greetings!!
Have a thought about how could we encourage more users to post and participate more on UNIX.com(because more we get questions, more we learn more), few are my ideas which I am posting feel free to add/edit more ideas in here. Keeping this as a POLL too.
I- Allow... (10 Replies)
Discussion started by: RavinderSingh13
10 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