File Manager

X7ROOT File Manager

Current Path: /opt/alt/ruby18/share/ri/1.8/system/Process

opt / alt / ruby18 / share / ri / 1.8 / system / Process /

ðŸ“ ..
ðŸ“ GID
ðŸ“ Status
ðŸ“ Sys
ðŸ“ UID
ðŸ“„ abort-c.yaml(395 B)
ðŸ“„ cdesc-Process.yaml(3.85 KB)
ðŸ“„ detach-c.yaml(1.91 KB)
ðŸ“„ egid%3d-c.yaml(315 B)
ðŸ“„ egid-c.yaml(454 B)
ðŸ“„ euid%3d-c.yaml(302 B)
ðŸ“„ euid-c.yaml(424 B)
ðŸ“„ exec-c.yaml(1.22 KB)
ðŸ“„ exit%21-c.yaml(421 B)
ðŸ“„ exit-c.yaml(1.35 KB)
ðŸ“„ fork-c.yaml(1.04 KB)
ðŸ“„ getpgid-c.yaml(421 B)
ðŸ“„ getpgrp-c.yaml(433 B)
ðŸ“„ getpriority-c.yaml(863 B)
ðŸ“„ getrlimit-c.yaml(868 B)
ðŸ“„ gid%3d-c.yaml(269 B)
ðŸ“„ gid-c.yaml(416 B)
ðŸ“„ groups%3d-c.yaml(536 B)
ðŸ“„ groups-c.yaml(417 B)
ðŸ“„ initgroups-c.yaml(837 B)
ðŸ“„ kill-c.yaml(963 B)
ðŸ“„ maxgroups%3d-c.yaml(330 B)
ðŸ“„ maxgroups-c.yaml(399 B)
ðŸ“„ pid-c.yaml(368 B)
ðŸ“„ ppid-c.yaml(609 B)
ðŸ“„ setpgid-c.yaml(366 B)
ðŸ“„ setpgrp-c.yaml(299 B)
ðŸ“„ setpriority-c.yaml(605 B)
ðŸ“„ setrlimit-c.yaml(2.41 KB)
ðŸ“„ setsid-c.yaml(457 B)
ðŸ“„ times-c.yaml(473 B)
ðŸ“„ uid%3d-c.yaml(312 B)
ðŸ“„ uid-c.yaml(414 B)
ðŸ“„ wait-c.yaml(2.17 KB)
ðŸ“„ wait2-c.yaml(772 B)
ðŸ“„ waitall-c.yaml(878 B)
ðŸ“„ waitpid-c.yaml(2.18 KB)
ðŸ“„ waitpid2-c.yaml(778 B)

Editing: detach-c.yaml

--- !ruby/object:RI::MethodDescription 
aliases: []

block_params: 
comment: 
- !ruby/struct:SM::Flow::P 
 body: Some operating systems retain the status of terminated child processes until the parent collects that status (normally using some variant of <tt>wait()</tt>. If the parent never collects this status, the child stays around as a zombie process. <tt>Process::detach</tt> prevents this by setting up a separate Ruby thread whose sole job is to reap the status of the process pid when it terminates. Use <tt>detach</tt> only when you do not intent to explicitly wait for the child to terminate. <tt>detach</tt> only checks the status periodically (currently once each second).
- !ruby/struct:SM::Flow::P 
 body: The waiting thread returns the exit status of the detached process when it terminates, so you can use <tt>Thread#join</tt> to know the result. If specified pid is not a valid child process ID, the thread returns <tt>nil</tt> immediately.
- !ruby/struct:SM::Flow::P 
 body: In this first example, we don't reap the first child process, so it appears as a zombie in the process status display.
- !ruby/struct:SM::Flow::VERB 
 body: " p1 = fork { sleep 0.1 }\n p2 = fork { sleep 0.2 }\n Process.waitpid(p2)\n sleep 2\n system(&quot;ps -ho pid,state -p #{p1}&quot;)\n"
- !ruby/struct:SM::Flow::P 
 body: produces:
- !ruby/struct:SM::Flow::VERB 
 body: " 27389 Z\n"
- !ruby/struct:SM::Flow::P 
 body: In the next example, <tt>Process::detach</tt> is used to reap the child automatically.
- !ruby/struct:SM::Flow::VERB 
 body: " p1 = fork { sleep 0.1 }\n p2 = fork { sleep 0.2 }\n Process.detach(p1)\n Process.waitpid(p2)\n sleep 2\n system(&quot;ps -ho pid,state -p #{p1}&quot;)\n"
- !ruby/struct:SM::Flow::P 
 body: (produces no output)
full_name: Process::detach
is_singleton: true
name: detach
params: |
 Process.detach(pid) => thread

visibility: public

X7ROOT File Manager

Editing: detach-c.yaml

Upload File

Create Folder