Linux velvet.gennetworks.in 4.18.0-553.83.1.lve.el8.x86_64 #1 SMP Wed Nov 12 10:04:12 UTC 2025 x86_64
LiteSpeed
Server IP : 161.129.70.235 & Your IP : 216.73.216.5
Domains :
Cant Read [ /etc/named.conf ]
User : virtueex
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
opt /
alt /
ruby18 /
share /
ri /
1.8 /
system /
Logger /
Delete
Unzip
Name
Size
Permission
Date
Action
Application
[ DIR ]
drwxr-xr-x
2026-02-18 15:11
Error
[ DIR ]
drwxr-xr-x
2026-02-18 15:11
Formatter
[ DIR ]
drwxr-xr-x
2026-02-18 15:11
LogDevice
[ DIR ]
drwxr-xr-x
2026-02-18 15:11
Severity
[ DIR ]
drwxr-xr-x
2026-02-18 15:11
ShiftingError
[ DIR ]
drwxr-xr-x
2026-02-18 15:11
%3c%3c-i.yaml
306
B
-rw-r--r--
2023-07-26 19:17
add-i.yaml
2.48
KB
-rw-r--r--
2023-07-26 19:17
cdesc-Logger.yaml
10.09
KB
-rw-r--r--
2023-07-26 19:17
close-i.yaml
226
B
-rw-r--r--
2023-07-26 19:17
datetime_format%3d-i.yaml
300
B
-rw-r--r--
2023-07-26 19:17
datetime_format-i.yaml
184
B
-rw-r--r--
2023-07-26 19:17
debug%3f-i.yaml
307
B
-rw-r--r--
2023-07-26 19:17
debug-i.yaml
322
B
-rw-r--r--
2023-07-26 19:17
error%3f-i.yaml
307
B
-rw-r--r--
2023-07-26 19:17
error-i.yaml
323
B
-rw-r--r--
2023-07-26 19:17
fatal%3f-i.yaml
307
B
-rw-r--r--
2023-07-26 19:17
fatal-i.yaml
322
B
-rw-r--r--
2023-07-26 19:17
format_message-i.yaml
216
B
-rw-r--r--
2023-07-26 19:17
format_severity-i.yaml
193
B
-rw-r--r--
2023-07-26 19:17
info%3f-i.yaml
304
B
-rw-r--r--
2023-07-26 19:17
info-i.yaml
1.06
KB
-rw-r--r--
2023-07-26 19:17
log-i.yaml
260
B
-rw-r--r--
2023-07-26 19:17
new-c.yaml
1.11
KB
-rw-r--r--
2023-07-26 19:17
unknown-i.yaml
383
B
-rw-r--r--
2023-07-26 19:17
warn%3f-i.yaml
304
B
-rw-r--r--
2023-07-26 19:17
warn-i.yaml
319
B
-rw-r--r--
2023-07-26 19:17
Save
Rename
--- !ruby/object:RI::MethodDescription aliases: [] block_params: comment: - !ruby/struct:SM::Flow::P body: Log an <tt>INFO</tt> message. - !ruby/struct:SM::Flow::P body: The message can come either from the <tt>progname</tt> argument or the <tt>block</tt>. If both are provided, then the <tt>block</tt> is used as the message, and <tt>progname</tt> is used as the program name. - !ruby/struct:SM::Flow::H level: 3 text: Examples - !ruby/struct:SM::Flow::VERB body: " logger.info("MainApp") { "Received connection from #{ip}" }\n # ...\n logger.info "Waiting for input from user"\n # ...\n logger.info { "User typed #{input}" }\n" - !ruby/struct:SM::Flow::P body: You'll probably stick to the second form above, unless you want to provide a program name (which you can do with <tt>Logger#progname=</tt> as well). - !ruby/struct:SM::Flow::H level: 3 text: Return - !ruby/struct:SM::Flow::P body: "See #add." full_name: Logger#info is_singleton: false name: info params: (progname = nil, &block) visibility: public