10-10-2013
How much memory do you have? What's your expected workload? What kind of performance does your application require? These questions are more relevant than the theoretical number of possible ldoms. The theoretical number is likely in the hundreds, but in the real world other limitations will come into play that make that unattainable.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
now, what do you define as core files.
there are some files outthere with the name perl.core, I-core.png, core.png
I mean, are these classified as core files too??? i thought core files are simply files called "core". Please help me out
this is urgent (2 Replies)
Discussion started by: TRUEST
2 Replies
2. Solaris
Setting up a T5240 with two disks c1t0d0 and c1t1d0.
I am trying to use raidctl but when I issue.
raidctl -l
I get
Controller 1
Disk: 0.0.0
Disk: 0.1.0
So I try
raidctl -c '0.0.0 0.1.0' -r 1 1
and I get "Array in use."
I try (4 Replies)
Discussion started by: photon
4 Replies
3. Solaris
its a fresh installation. during the OS setup, it did not prompt for IP, netmask and gateway. using Solaris 10 08/07 update 4. I tried to plumb manually but encountered no such interface error. but nxge interfaces can be greped from the /etc/path_to_inst file.
getting similar error on... (3 Replies)
Discussion started by: incredible
3 Replies
4. Solaris
Hi,
We are planning to buy new server for our data center. Sun T5240 or M3000 which one have better performance, we are going to create many dt sessions in this server. So, i need your suggestions.
RJS (4 Replies)
Discussion started by: rajasekg
4 Replies
5. Solaris
Hi Friends
we have sun T5240 server, we have taken ufsdump of this server remotely with scsi tapedrive, If we need to do ufsrestore means what we have to do, since T5240 has not having scsi port, any procedure is there?
Regards
Rajasekar (5 Replies)
Discussion started by: rajasekg
5 Replies
6. Solaris
Hi Gurus
Can any one tell me the process of disabling the multithreading option on T5240 server and my OS is on LDOM, having one physical processor with 8 core & 8 thread per core
Regards (3 Replies)
Discussion started by: amity
3 Replies
7. Solaris
Hi !
I've been given a T5240 with 4 disks and 2 HBA cards (but no array connected). I did a factory reset on SP and NVRAM clean on OBP because the server had been used before.
I boot cdrom in single mode and try to create a hw mirror with disks from c1... but only c2 is seen by raidctl.
... (2 Replies)
Discussion started by: delavega
2 Replies
8. Solaris
Hi
I need to reduce cores on T5240 server for meeting Oracle Core licenses. For that I have install the LDOM packages & run below mention commands.
bash-3.2# ldm list-config
factory-default
config_initial
bash-3.2# ldm set-vcpu 32 primary
bash-3.2# ldm list-config... (5 Replies)
Discussion started by: amity
5 Replies
9. Solaris
Hi Folks,
Just a quick question - hopefully!
I have an application currently running on a V890 with Solaris 9, I'd like to move this to either one of our T-5's or one of the T5240's in a Legacy container on an LDOM - but the fly in the ointment is the application still uses a standard Hayes... (3 Replies)
Discussion started by: gull04
3 Replies
LEARN ABOUT FREEBSD
crashinfo
CRASHINFO(8) BSD System Manager's Manual CRASHINFO(8)
NAME
crashinfo -- analyze a core dump of the operating system
SYNOPSIS
crashinfo [-d crashdir] [-n dumpnr] [-k kernel] [core]
DESCRIPTION
The crashinfo utility analyzes a core dump saved by savecore(8). It generates a text file containing the analysis in the same directory as
the core dump. For a given core dump file named vmcore.XX the generated text file will be named core.txt.XX.
By default, crashinfo analyzes the most recent core dump in the core dump directory. A specific core dump may be specified via either the
core or dumpnr arguments. Once crashinfo has located a core dump, it analyzes the core dump to determine the exact version of the kernel
that generated the core. It then looks for a matching kernel file under each of the subdirectories in /boot. The location of the kernel
file can also be explicitly provided via the kernel argument.
Once crashinfo has located a core dump and kernel, it uses several utilities to analyze the core including dmesg(8), fstat(1), iostat(8),
ipcs(1), kgdb(1), netstat(1), nfsstat(1), ps(1), pstat(8), and vmstat(8).
The options are as follows:
-d crashdir
Specify an alternate core dump directory. The default crash dump directory is /var/crash.
-n dumpnr
Use the core dump saved in vmcore.dumpnr instead of the latest core in the core dump directory.
-k kernel
Specify an explicit kernel file.
SEE ALSO
textdump(4), savecore(8)
HISTORY
The crashinfo utility appeared in FreeBSD 6.4.
BSD
June 28, 2008 BSD