Linux server.bornosky.com 4.18.0-477.13.1.lve.el8.x86_64 #1 SMP Thu Jun 1 16:40:47 EDT 2023 x86_64
Apache
: 95.217.200.235 | : 3.149.214.28
Cant Read [ /etc/named.conf ]
7.3.33
aggscedu
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
lib /
rpm /
macros.d /
[ HOME SHELL ]
Name
Size
Permission
Action
macros.dwz
1.76
KB
-rw-r--r--
macros.efi-srpm
3
KB
-rw-r--r--
macros.environment-modules
75
B
-rw-r--r--
macros.fedora-misc
2.76
KB
-rw-r--r--
macros.fedora-misc-srpm
239
B
-rw-r--r--
macros.forge
12.43
KB
-rw-r--r--
macros.ghc-srpm
414
B
-rw-r--r--
macros.go-srpm
7.17
KB
-rw-r--r--
macros.info
390
B
-rw-r--r--
macros.kernel-srpm
116
B
-rw-r--r--
macros.ldc-srpm
73
B
-rw-r--r--
macros.ldconfig
307
B
-rw-r--r--
macros.mono-srpm
181
B
-rw-r--r--
macros.nodejs-srpm
324
B
-rw-r--r--
macros.ocaml-srpm
737
B
-rw-r--r--
macros.openblas-srpm
104
B
-rw-r--r--
macros.perl
5.06
KB
-rw-r--r--
macros.perl-srpm
794
B
-rw-r--r--
macros.pybytecompile
886
B
-rw-r--r--
macros.python
3.36
KB
-rw-r--r--
macros.python-srpm
5.95
KB
-rw-r--r--
macros.python2
1.82
KB
-rw-r--r--
macros.python3
3.63
KB
-rw-r--r--
macros.rust-srpm
61
B
-rw-r--r--
macros.scl
13.53
KB
-rw-r--r--
macros.selinux-policy
6.62
KB
-rw-r--r--
macros.systemd
4.03
KB
-rw-r--r--
macros.systemtap
206
B
-rw-r--r--
macros.valgrind-srpm
127
B
-rw-r--r--
macros.vpath
228
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : macros.dwz
# Macros for reducing debug info size using dwz(1) utility. # The two default values below should result in dwz taking at most # 3GB of RAM or so on 64-bit hosts and 2.5GB on 32-bit hosts # on the largest *.debug files (in mid 2012 those are # libreoffice-debuginfo, debuginfos containing # libxul.so.debug and libwebkitgtk-*.so.*.debug). # This needs to be tuned based on the amount of available RAM # on build boxes for each architecture as well as virtual address # space limitations if dwz is 32-bit program. While it needs less # memory than 64-bit program because pointers are smaller, it can # never have more than 4GB-epsilon of RAM and on some architecture # even less than that (e.g. 2GB). # Number of debugging information entries (DIEs) above which # dwz will stop considering file for multifile optimizations # and enter a low memory mode, in which it will optimize # in about half the memory needed otherwise. %_dwz_low_mem_die_limit 10000000 # Number of DIEs above which dwz will stop processing # a file altogether. %_dwz_max_die_limit 50000000 # On x86_64 increase the higher limit to make libwebkit* optimizable. # libwebkit* in mid 2012 contains roughly 87mil DIEs, and 64-bit # dwz is able to optimize it from ~1.1GB to ~410MB using 5.2GB of RAM. %_dwz_max_die_limit_x86_64 110000000 # On ARM, build boxes often have only 512MB of RAM and are very slow. # Lower both the limits. %_dwz_low_mem_die_limit_armv5tel 4000000 %_dwz_low_mem_die_limit_armv7hl 4000000 %_dwz_max_die_limit_armv5tel 10000000 %_dwz_max_die_limit_armv7hl 10000000 %_dwz_limit() %{expand:%%{?%{1}_%{_arch}}%%{!?%{1}_%{_arch}:%%%{1}}} %_find_debuginfo_dwz_opts --run-dwz\\\ --dwz-low-mem-die-limit %{_dwz_limit _dwz_low_mem_die_limit}\\\ --dwz-max-die-limit %{_dwz_limit _dwz_max_die_limit}
Close