| Server IP : 103.119.228.120 / Your IP : 3.21.46.68 Web Server : Apache System : Linux v8.techscape8.com 3.10.0-1160.119.1.el7.tuxcare.els2.x86_64 #1 SMP Mon Jul 15 12:09:18 UTC 2024 x86_64 User : nobody ( 99) PHP Version : 5.6.40 Disable Function : shell_exec,symlink,system,exec,proc_get_status,proc_nice,proc_terminate,define_syslog_variables,syslog,openlog,closelog,escapeshellcmd,passthru,ocinum cols,ini_alter,leak,listen,chgrp,apache_note,apache_setenv,debugger_on,debugger_off,ftp_exec,dl,dll,myshellexec,proc_open,socket_bind,proc_close,escapeshellarg,parse_ini_filepopen,fpassthru,exec,passthru,escapeshellarg,escapeshellcmd,proc_close,proc_open,ini_alter,popen,show_source,proc_nice,proc_terminate,proc_get_status,proc_close,pfsockopen,leak,apache_child_terminate,posix_kill,posix_mkfifo,posix_setpgid,posix_setsid,posix_setuid,dl,symlink,shell_exec,system,dl,passthru,escapeshellarg,escapeshellcmd,myshellexec,c99_buff_prepare,c99_sess_put,fpassthru,getdisfunc,fx29exec,fx29exec2,is_windows,disp_freespace,fx29sh_getupdate,fx29_buff_prepare,fx29_sess_put,fx29shexit,fx29fsearch,fx29ftpbrutecheck,fx29sh_tools,fx29sh_about,milw0rm,imagez,sh_name,myshellexec,checkproxyhost,dosyayicek,c99_buff_prepare,c99_sess_put,c99getsource,c99sh_getupdate,c99fsearch,c99shexit,view_perms,posix_getpwuid,posix_getgrgid,posix_kill,parse_perms,parsesort,view_perms_color,set_encoder_input,ls_setcheckboxall,ls_reverse_all,rsg_read,rsg_glob,selfURL,dispsecinfo,unix2DosTime,addFile,system,get_users,view_size,DirFiles,DirFilesWide,DirPrintHTMLHeaders,GetFilesTotal,GetTitles,GetTimeTotal,GetMatchesCount,GetFileMatchesCount,GetResultFiles,fs_copy_dir,fs_copy_obj,fs_move_dir,fs_move_obj,fs_rmdir,SearchText,getmicrotime MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/gdbm-1.10/ |
Upload File : |
****************************************************************************** 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).