查看网站首页
查看网站首页
查看 sitemap.xml
✏️ 正在编辑: cdesc-Signal.yaml
路径:
/opt/alt/ruby18/share/ri/1.8/system/Signal/cdesc-Signal.yaml
提示:
您可以编辑任何文件(包括二进制文件),但请注意不当修改可能导致文件损坏。
--- !ruby/object:RI::ClassDescription attributes: [] class_methods: - !ruby/object:RI::MethodSummary name: list - !ruby/object:RI::MethodSummary name: trap comment: - !ruby/struct:SM::Flow::P body: Many operating systems allow signals to be sent to running processes. Some signals have a defined effect on the process, while others may be trapped at the code level and acted upon. For example, your process may trap the USR1 signal and use it to toggle debugging, and may use TERM to initiate a controlled shutdown. - !ruby/struct:SM::Flow::VERB body: " pid = fork do\n Signal.trap("USR1") do\n $debug = !$debug\n puts "Debug now: #$debug"\n end\n Signal.trap("TERM") do\n puts "Terminating..."\n shutdown()\n end\n # . . . do some work . . .\n end\n\n Process.detach(pid)\n\n # Controlling program:\n Process.kill("USR1", pid)\n # ...\n Process.kill("USR1", pid)\n # ...\n Process.kill("TERM", pid)\n" - !ruby/struct:SM::Flow::P body: "produces:" - !ruby/struct:SM::Flow::VERB body: " Debug now: true\n Debug now: false\n Terminating...\n" - !ruby/struct:SM::Flow::P body: The list of available signal names and their interpretation is system dependent. Signal delivery semantics may also vary between systems; in particular signal delivery may not always be reliable. constants: [] full_name: Signal includes: [] instance_methods: [] name: Signal superclass:
💾 保存文件
← 返回文件管理器