Mailing List
Home
Forum Home
Linux - General Red Hat Linux discussion list
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Installation - Getting started with Red Hat Linux
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
about process

about process

2005-08-12       - By Eris

 Back
Reply:     1     2  

On Friday 12 August 2005 12:08 am, peeyush kr wrote:
> Hi friends,
>
> I want to know about the process that run in the background.
> there are three processes  1.active  2.sleep  3. zombi

When a process is active then it is actually executing on the CPU.  An active
process has it's program code loaded into RAM.

When a process is sleeping, then it is not executing.  Instead it is waiting
for something to happen.  It may be waiting for the disk controller to read
data off of the hard disk, or it may be waiting for data to arrive on the
ethernet port.  A process can sleep for many different reasons.  A process
that is sleeping may have it's code and data moved out of RAM and onto the
swap partition if it has been waiting long enough.

A zombie process is one that has already terminated and been unloaded from
RAM, so it isn't using your memory.  But it is still listed in the process
list because no one has checked its return value yet.  (The return value is
stored in the process table entry, so that entry has to be kept around until
the return value is checked, even if the process itself is already unloaded
from RAM.)

Normally a zombie process will disappear very quickly because the init process
itself will remove it if no other program checks the return value.  If the
zombie stays around, then it is usually because its parent process is still
running, but is not checking the return value.  In that case you have to kill
the parent in order to kill the zombie.

Eris Caffee

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@(protected)?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

Earn $52 per hosting referral at Lunarpages.