12-10-2008
My apologies,
I don't think that should work in this case. I've tried it on my server yesterday. Things go non related. But, proceed checking hardware.
-DB
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
system:
HP-UX 10.20 with HFS mounted.
How can I convert the HFS to VxFS without an ignite server ?
Is this possible ?
thanks
simon2000 (4 Replies)
Discussion started by: simon2000
4 Replies
2. UNIX for Advanced & Expert Users
I know and used an ignite server for hp-ux, but is there such a beast for Solaris flavour of unix ?
thanks
simon (1 Reply)
Discussion started by: simon2000
1 Replies
3. HP-UX
Sorry if this has been asked and answered, but I can't find this particual problem. I've had an Ignite server running for years on a small internal network with images we load on daily basis. Tried to load two servers, L2000 and C3600 , both with same problem.
# boot lan.192.168.2.2 install
... (0 Replies)
Discussion started by: ddeblance
0 Replies
4. HP-UX
hi,
I am using HPUX 11.31(Itanium) and HP 5100 printer.
I am using PCL5.nloo model script present in HPUX by default to print to printer.
I am finding issues in printing paper sizes and few other options.
Description of the problem:
When i give a print with option "half" and "Legal"... (4 Replies)
Discussion started by: meeraramanathan
4 Replies
5. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
6. Shell Programming and Scripting
Hi,
While trying to supress password prompt using ssh. I have added .ssh folder manually and generated public key and added to authorized_keys file in the remote machine. But still it's prompting for passwords with the following message:
Permission denied... (5 Replies)
Discussion started by: 116@434
5 Replies
7. HP-UX
I try to start a integrity vm machine using ignite-ux
and my usual dhcp server on linux.
Ip of server ignite is =192.168.0.16
Ip of dhcpd is = 192.168.0.2
Ip of client vm = 192.168.0.18
I try to boot from lan
Booting over the network
Loading.: lanboot
Client MAC Address: XXXXXXXXXX ..... (5 Replies)
Discussion started by: Linusolaradm1
5 Replies
8. HP-UX
Hi all,
There wasn't nsswitch.conf file in my HPUX server. So I copied /etc/nsswitch.files to /etc/nsswitch.conf and changed the content like below.
passwd: compat
group: compat
hosts: files dns nis
ipnodes: dns files
services: nis files
networks: nis... (2 Replies)
Discussion started by: sembii
2 Replies
9. HP-UX
On one of the Hpvm server when I try to do the ignite recovery it aborts after recovering only 30 % of the archive. I do not have any other archive backup besides this.
Even after restoring the 30 archive I could see that I am able to login to that server althoug ssh and other functionalities... (9 Replies)
Discussion started by: kpatel786
9 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