deadlock n.
1. [techspeak] A situation wherein two or more
processes are unable to proceed because each is waiting for one of
the others to do something. A common example is a program
communicating to a server, which may find itself waiting for output
from the server before sending anything more to it, while the
server is similarly waiting for more input from the controlling
program before outputting anything. (It is reported that this
particular flavor of deadlock is sometimes called a `starvation
deadlock', though the term `starvation' is more properly used for
situations where a program can never run simply because it never
gets high enough priority. Another common flavor is
`constipation', in which each process is trying to send stuff to
the other but all buffers are full because nobody is reading
anything.) See deadly embrace. 2. Also used of deadlock-like
interactions between humans, as when two people meet in a narrow
corridor, and each tries to be polite by moving aside to let the
other pass, but they end up swaying from side to side without
making any progress because they always move the same way at the
same time.
1. [techspeak] A situation wherein two or more
processes are unable to proceed because each is waiting for one of
the others to do something. A common example is a program
communicating to a server, which may find itself waiting for output
from the server before sending anything more to it, while the
server is similarly waiting for more input from the controlling
program before outputting anything. (It is reported that this
particular flavor of deadlock is sometimes called a `starvation
deadlock', though the term `starvation' is more properly used for
situations where a program can never run simply because it never
gets high enough priority. Another common flavor is
`constipation', in which each process is trying to send stuff to
the other but all buffers are full because nobody is reading
anything.) See deadly embrace. 2. Also used of deadlock-like
interactions between humans, as when two people meet in a narrow
corridor, and each tries to be polite by moving aside to let the
other pass, but they end up swaying from side to side without
making any progress because they always move the same way at the
same time.
Related:
- deadlock: n. 1. [techspeak] A situation wherein two or more
processes are unable to proceed because each is waiting for one of
the others to do something
A common example is a program communicating to a... - livelock /li:v'lok/ n.
A situation in which some critical
stage of a task is unable to finish because its clients perpetually
create more work for it to do after they have been serviced but
before it can clear its queue
Differs from deadlock in that the process is not... - livelock: /li:v'lok/ n. A situation in which some critical stage
of a task is unable to finish because its clients perpetually
create more work for it to do after they have been serviced but
before it can clear its queue
Differs from {deadlock} in that the process is not... - deadly embrace n.
Same as deadlock, though usually
used only when exactly two processes are involved
This is the more popular term in Europe, while deadlock... - deadly embrace: n. Same as {deadlock}, though usually used only when
exactly two processes are involved
This is the more popular term in Europe, while {deadlock}... - shell [orig. Multics n.
techspeak, widely propagated
via Unix] 1
[techspeak] The command interpreter used to pass ... - wedged: adj. 1. To be stuck, incapable of proceeding without
help
This is different from having crashed. If the system... - hung adj.
[from `hung up'; common] Equivalent to
wedged
but more common at Unix/C sites. Not generally used... - talk mode n.
A feature supported by Unix, ITS, and some
other OSes that allows two or more logged-in users to set up a
real-time on-line conversation
It combines the immediacy of talking with all the...
