Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 3.17.176.160
Domains :
Cant Read [ /etc/named.conf ]
User : web
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
gawk-4.0.2 /
Delete
Unzip
Name
Size
Permission
Date
Action
COPYING
34.32
KB
-rw-r--r--
2012-12-03 21:03
FUTURES
2.02
KB
-rw-r--r--
2012-12-25 18:31
LIMITATIONS
891
B
-rw-r--r--
2012-12-25 18:31
NEWS
4.75
KB
-rw-r--r--
2012-12-25 18:31
POSIX.STD
1.64
KB
-rw-r--r--
2012-12-03 21:03
README
3.3
KB
-rw-r--r--
2012-12-23 13:31
README.multibyte
1.11
KB
-rw-r--r--
2012-05-03 18:13
README.tests
1.29
KB
-rw-r--r--
2012-05-03 18:13
Save
Rename
Fri Jun 3 12:20:17 IDT 2005 ============================ As noted in the NEWS file, as of 3.1.5, gawk uses character values instead of byte values for `index', `length', `substr' and `match'. This works in multibyte and unicode locales. Wed Jun 18 16:47:31 IDT 2003 ============================ Multibyte locales can cause occasional weirdness, in particular with ranges inside brackets: /[....]/. Something that works great for ASCII will choke for, e.g., en_US.UTF-8. One such program is test/gsubtst5.awk. By default, the test suite runs with LC_ALL=C and LANG=C. You can change this by doing (from a Bourne-style shell): $ GAWKLOCALE=some_locale make check Then the test suite will set LC_ALL and LANG to the given locale. As of this writing, this works for en_US.UTF-8, and all tests pass except gsubtst5. For the normal case of RS = "\n", the locale is largely irrelevant. For other single byte record separators, using LC_ALL=C will give you much better performance when reading records. Otherwise, gawk has to make several function calls, *per input character* to find the record terminator. You have been warned.