Linux premium71.web-hosting.com 4.18.0-513.11.1.lve.el8.x86_64 #1 SMP Thu Jan 18 16:21:02 UTC 2024 x86_64
LiteSpeed
Server IP : 198.187.29.8 & Your IP : 216.73.216.155
Domains :
Cant Read [ /etc/named.conf ]
User : cleahvkv
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
opt /
alt /
ruby18 /
share /
ri /
1.8 /
system /
Signal /
Delete
Unzip
Name
Size
Permission
Date
Action
cdesc-Signal.yaml
1.51
KB
-rw-r--r--
2023-07-26 13:47
list-c.yaml
1.14
KB
-rw-r--r--
2023-07-26 13:47
trap-c.yaml
1.36
KB
-rw-r--r--
2023-07-26 13:47
Save
Rename
--- !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: