10-24-2014
Moving lwps from core to core can reduce cache hits, so the dispatching logic may look at longer term stats before reassigning a lwp.
8 More Discussions You Might Find Interesting
1. IP Networking
Ok, I've read the manpages on netstat and it gives a good description of the state values such as CLOSE_WAIT, ESTABLISHED, SYN_RECEIVED, etc..
Can someone give me real world situations where you would get these states. LIke for example if I got SYN_RECEIVED what possible situations would be the... (1 Reply)
Discussion started by: eloquent99
1 Replies
2. Solaris
Hi Everybody,
As I am new to Sun Clusters, Please help me what is "online but not monitored" state of resources and "online - service is online" in status message. Thank you. (1 Reply)
Discussion started by: mayahari
1 Replies
3. UNIX for Dummies Questions & Answers
Not really a newbie, but I have a strange problem and I'm not sure how to further troubleshoot it.
I have to log out of a virtual terminal by typing exit, then exit again as in:
woodnt@toshiba-laptop ~ $ exit
logout
woodnt@toshiba-laptop ~ $ exit
logout
I DON'T have to do this when I'm... (1 Reply)
Discussion started by: Narnie
1 Replies
4. UNIX for Advanced & Expert Users
I am trying to write my own Unix compliant (SUSv4) OS - Just a hobby OS, nothing serious. While going through the standard, I couldn't find any explicit information on process states. What I could find was (excluding the real-time considerations)-
From this it can be inferred that the... (2 Replies)
Discussion started by: tinkerbeast
2 Replies
5. Solaris
Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12).
I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Discussion started by: Matt_VB
4 Replies
6. Shell Programming and Scripting
netstat | awk '/server/ {for(i=1;i<2;i++) {getline;print}'
Output:
ESTABLISHED
ESTABLISHED
ESTABLISHED
ESTABLISHED
ESTABLISHED
TIME_WAIT
TIME_WAIT
From the above command I'm getting all the states. I want to count the states and write to a file, like
"Count of ESTABLISHED... (6 Replies)
Discussion started by: Roozo
6 Replies
7. Shell Programming and Scripting
I am using HP-UX,KSH
$ jobs -l
+ 19377 Running nohup ksh cat_Duplicate_Records_Removal.ksh </dev/null >/dev/null 2>&1 &
$ ps -p 19377 -fl
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME COMD
401 S catmgr 19377 19491 ... (1 Reply)
Discussion started by: TomG
1 Replies
8. UNIX for Beginners Questions & Answers
Hi All,
Is there any way I can prioritize my VMs when there is resource crunch in host machine so that some VMs will be allocated more vcpu, more memory than other VMs in kvm/qemu hypervisor based virtual machines?
Lets say in my cloud environment my Ubuntu 16 compute hosts are running some... (0 Replies)
Discussion started by: SanjayK
0 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