Sets limits for the current process for the given resource to cur_limit (soft limit) and max_limit (hard limit); returns nil.
Argument resource specifies the resource whose limits are to be set; the argument may be given as a symbol, as a string, or as a constant beginning with Process::RLIMIT_ (e.g., :CORE, 'CORE', or Process::RLIMIT_CORE.
The resources available and supported are system-dependent, and may include (here expressed as symbols):
:AS: Total available memory (bytes) (SUSv3, NetBSD, FreeBSD, OpenBSD except 4.4BSD-Lite).
:CORE: Core size (bytes) (SUSv3).
:CPU: CPU time (seconds) (SUSv3).
:DATA: Data segment (bytes) (SUSv3).
:FSIZE: File size (bytes) (SUSv3).
:MEMLOCK: Total size for mlock(2) (bytes) (4.4BSD, GNU/Linux).
:MSGQUEUE: Allocation for POSIX message queues (bytes) (GNU/Linux).
:NICE: Ceiling on process’s nice(2) value (number) (GNU/Linux).
:NOFILE: File descriptors (number) (SUSv3).
:NPROC: Number of processes for the user (number) (4.4BSD, GNU/Linux).
:NPTS: Number of pseudo terminals (number) (FreeBSD).
:RSS: Resident memory size (bytes) (4.2BSD, GNU/Linux).
:RTPRIO: Ceiling on the process’s real-time priority (number) (GNU/Linux).
:RTTIME: CPU time for real-time process (us) (GNU/Linux).
:SBSIZE: All socket buffers (bytes) (NetBSD, FreeBSD).
:SIGPENDING: Number of queued signals allowed (signals) (GNU/Linux).
:STACK: Stack size (bytes) (SUSv3).
Arguments cur_limit and max_limit may be:
Integers (max_limit should not be smaller than cur_limit).
Symbol :SAVED_MAX, string 'SAVED_MAX', or constant Process::RLIM_SAVED_MAX: saved maximum limit.
Symbol :SAVED_CUR, string 'SAVED_CUR', or constant Process::RLIM_SAVED_CUR: saved current limit.
Symbol :INFINITY, string 'INFINITY', or constant Process::RLIM_INFINITY: no limit on resource.
This example raises the soft limit of core size to the hard limit to try to make core dump possible:
Process.setrlimit(:CORE, Process.getrlimit(:CORE)[1])
Not available on all platforms.
Returns a list of signal names mapped to the corresponding underlying signal numbers.
Signal.list #=> {"EXIT"=>0, "HUP"=>1, "INT"=>2, "QUIT"=>3, "ILL"=>4, "TRAP"=>5, "IOT"=>6, "ABRT"=>6, "FPE"=>8, "KILL"=>9, "BUS"=>7, "SEGV"=>11, "SYS"=>31, "PIPE"=>13, "ALRM"=>14, "TERM"=>15, "URG"=>23, "STOP"=>19, "TSTP"=>20, "CONT"=>18, "CHLD"=>17, "CLD"=>17, "TTIN"=>21, "TTOU"=>22, "IO"=>29, "XCPU"=>24, "XFSZ"=>25, "VTALRM"=>26, "PROF"=>27, "WINCH"=>28, "USR1"=>10, "USR2"=>12, "PWR"=>30, "POLL"=>29}
Compile a ImplicitRestNode node
Compile a SourceLineNode node
Dispatch enter and leave events for ImplicitRestNode nodes and continue walking the tree.
Dispatch enter and leave events for SourceLineNode nodes and continue walking the tree.
Inspect a ImplicitRestNode node.
Inspect a SourceLineNode node.
Scanning is intentionally conservative because we have no way of rolling back an aggressive block (at this time)
If a block was stopped for some trivial reason, (like an empty line) but the next line would have caused it to be balanced then we can check that condition and grab just one more line either up or down.
For example, below if we’re scanning up, line 2 might cause the scanning to stop. This is because empty lines might denote logical breaks where the user intended to chunk code which is a good place to stop and check validity. Unfortunately it also means we might have a “dangling” keyword or end.
1 def bark 2 3 end
If lines 2 and 3 are in the block, then when this method is run it would see it is unbalanced, but that acquiring line 1 would make it balanced, so that’s what it does.
See the OpenSSL documentation for EVP_PKEY_new_raw_public_key()
Serializes the public key to DER-encoded X.509 SubjectPublicKeyInfo format.
Serializes the public key to PEM-encoded X.509 SubjectPublicKeyInfo format.
A PEM-encoded key will look like:
-----BEGIN PUBLIC KEY----- [...] -----END PUBLIC KEY-----
See the OpenSSL documentation for EVP_PKEY_get_raw_public_key()
Expands lazy enumerator to an array. See Enumerable#to_a.
Indicated whether this Cipher instance uses an Authenticated Encryption mode.