sleep vi. 1. [techspeak] To relinquish a claim (of a process on a multitasking system) for service;

sleep vi.

1. [techspeak] To relinquish a claim (of a
process on a multitasking system) for service; to indicate to the
scheduler that a process may be deactivated until some given event
occurs or a specified time delay elapses. 2. In jargon, used very
similarly to v. block; also in `sleep on', syn. with
`block on'. Often used to indicate that the speaker has
relinquished a demand for resources until some (possibly
unspecified) external event: "They can't get the fix I've been
asking for into the next release, so I'm going to sleep on it until
the release, then start hassling them again."

Related:

• sleep: vi. 1. [techspeak] To relinquish a claim (of a process on a multitasking system) for service;
  to indicate to the scheduler that a process may...
• snark n. [Lewis Carroll, via the Michigan Terminal System] 1.
  A system failure. When a user's process bombed, the...
• snark: [Lewis Carroll, via the Michigan Terminal System] n.
  1. A system failure. When a user's process bombed...
• fried: adj. 1. Non-working due to hardware failure;
  burnt out. Especially used of hardware brought down...
• block v. [common; from process scheduling terminology in OS theory] 1.
  vi. To delay or sit idle while waiting for something...
• fried adj. 1. [common] Non-working due to hardware failure;
  burnt out. Especially used of hardware brought down...
• hang v. 1. [very common] To wait for an event that will never occur.
  "The system is hanging because it can't read from ...
• block: [from process scheduling terminology in OS theory] 1.
  vi. To delay or sit idle while waiting for something...
• hang: v. 1. To wait for an event that will never occur.
  "The system is hanging because it can't read from...