Sponsored Content
Full Discussion: sun v240 performance
Operating Systems Solaris sun v240 performance Post 302398163 by naw_deepak on Wednesday 24th of February 2010 01:53:28 AM
Old 02-24-2010
You have 68 zombie process in your server which causes the performance degrade. Please kill all these processes and check if becomes normal.

Thanks,
Deepak
 

9 More Discussions You Might Find Interesting

1. Solaris

Enhance Sun Solaris 10 performance ?

Guys where can i find values to add in /etc/system to make sun solaris 10 working better ? im sure there is alot of values but i dont know from where i can find them if you know any please send direct and if you know another sites send links to it, thanks so much. (5 Replies)
Discussion started by: XP_2600
5 Replies

2. UNIX for Advanced & Expert Users

Help: Sun Disk partitioning for Sun V240 & StorEdge 3300

Dear Sun gurus, I have Sun Fire V240 server with its StorEdge 3300 disk-array. Following are its disks appeared in format command. I have prepared its partitions thru format and metainit & metattach (may be i have made wrong steps, causing the errors below because I have done thru some document... (1 Reply)
Discussion started by: shafeeq
1 Replies

3. Solaris

Sun T1000 application low performance

Hello All. I have Sun T1000 server with Solaris 10. On T1000 installed EMC smarts, application for monitoring network devices via SNMP + SNMP. So, Smarts has own DB (contains object - devices and relationships), file takes 30 mb, now, all queries to DB works very slow, so Smarts works too slow,... (5 Replies)
Discussion started by: hemulll
5 Replies

4. Filesystems, Disks and Memory

Poor read performance on sun storedge a1000

Hello, i have a a1000 connected to an e6500. There's a raid 10 (12 disks) on the a1000. If i do a dd if=/dev/zero of=/mnt/1 bs=1024k count=1000 and then look at iostat it tells me there's a kw/s of 25000. But if i do a dd of=/dev/zero if=/mnt/1 bs=1024k count=1000 then i see only a... (1 Reply)
Discussion started by: mbrenner
1 Replies

5. Solaris

BIOS Serial Number on Sun Fire V240

Hi, I want to know if there is a command available for obtaining the BIOS Serial Number on a Sun Fire V240 machine? Or is it a known issue that it cannot be obtained through any command? Thanks, Vineet (4 Replies)
Discussion started by: vineetd
4 Replies

6. Solaris

Alom Sun V240

hallo anybody know how to set alom mail alerty server with yahoomail ? thank u?where i can find mail server address for yahoomail?thank (1 Reply)
Discussion started by: yanto85
1 Replies

7. Solaris

Sun Fire V240 server Fan replacement

I have a sun fire v240 server. The output of prtdiag -v shows a failed fan. There are 3 fans for cooling system board. There is 1 fan for each of the powersupply (There are 2 powersupplies) From the below output how do i know which fan is bad and whats its location... (3 Replies)
Discussion started by: Tirmazi
3 Replies

8. Solaris

Sun V240 Raid Question

Hi All, I'm new to this site. I have a few question since I'm in the process how to to repair my raid on Sun V240 Server. 1. How can we create RAID in Sun Sparc v240? 2. What utility can help people create RAID in Sun Sparc v240? 3. Do we need any special software to create the... (12 Replies)
Discussion started by: angkor
12 Replies

9. Solaris

Sun T1000 performance

Hi If you had a choice of processor for a general purpose web server, either: A. T1, 8-core. (in a T1000, 8GB, 72GB SAS x 2) or B. Dual 1.6GHZ USIIIi (in a Sun Blade 2500 Silver Workstation, 4GB, 146GB SCSI) Would A be significantly better than B? Even on single-threaded tasks? I... (0 Replies)
Discussion started by: edik
0 Replies
KILLALL(1)						    BSD General Commands Manual 						KILLALL(1)

NAME
killall -- kill processes by name SYNOPSIS
killall [-delmsvz] [-help] [-I] [-j jail] [-u user] [-t tty] [-c procname] [-SIGNAL] [procname ...] DESCRIPTION
The killall utility kills processes selected by name, as opposed to the selection by PID as done by kill(1). By default, it will send a TERM signal to all processes with a real UID identical to the caller of killall that match the name procname. The super-user is allowed to kill any process. The options are as follows: -d | -v Be more verbose about what will be done. For a single -d option, a list of the processes that will be sent the signal will be printed, or a message indicating that no matching processes have been found. -e Use the effective user ID instead of the (default) real user ID for matching processes specified with the -u option. -help Give a help on the command usage and exit. -I Request confirmation before attempting to signal each process. -l List the names of the available signals and exit, like in kill(1). -m Match the argument procname as a (case sensitive) regular expression against the names of processes found. CAUTION! This is dangerous, a single dot will match any process running under the real UID of the caller. -s Show only what would be done, but do not send any signal. -SIGNAL Send a different signal instead of the default TERM. The signal may be specified either as a name (with or without a leading ``SIG''), or numerically. -j jail Kill processes in the specified jail. -u user Limit potentially matching processes to those belonging to the specified user. -t tty Limit potentially matching processes to those running on the specified tty. -c procname Limit potentially matching processes to those matching the specified procname. -q Suppress error message if no processes are matched. -z Do not skip zombies. This should not have any effect except to print a few error messages if there are zombie processes that match the specified pattern. ALL PROCESSES
Sending a signal to all processes with the given UID is already supported by kill(1). So use kill(1) for this job (e.g. ``kill -TERM -1'' or as root ``echo kill -TERM -1 | su -m <user>''). IMPLEMENTATION NOTES
This FreeBSD implementation of killall has completely different semantics as compared to the traditional UNIX System V behavior of killall. The latter will kill all processes that the current user is able to kill, and is intended to be used by the system shutdown process only. EXIT STATUS
The killall utility exits 0 if some processes have been found and signalled successfully. Otherwise, a status of 1 will be returned. DIAGNOSTICS
Diagnostic messages will only be printed if requested by -d options. SEE ALSO
kill(1), pkill(1), sysctl(3), jail(8) HISTORY
The killall command appeared in FreeBSD 2.1. It has been modeled after the killall command as available on other platforms. AUTHORS
The killall program was originally written in Perl and was contributed by Wolfram Schneider, this manual page has been written by Jorg Wunsch. The current version of killall was rewritten in C by Peter Wemm using sysctl(3). BSD
June 30, 2013 BSD
All times are GMT -4. The time now is 07:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy