The Remote Gnu Database Manager is a client library and network server daemon used for managing the GNU GDBM(3) database management system. It enables remote access of the database, facilitating efficient and secure management of data.
Remote Gnu Database Manager is a powerful network server daemon and client library that utilizes the standard GNU GDBM(3) database management interface, which incorporates Berkeley DBM. The software is relatively easy to set up after installation, with steps outlined for versions 2.1.33 or later.
The first step is to create a user, "gdbm," on the server machine with home in "/var/lib/gdbm." Typically, this is taken care of by the "make install" function, which utilizes "adduser." However, it's recommended that you check "/etc/passwd" and "/etc/group" to ensure everything is set up correctly.
Next, create directories "/var/lib/gdbm," "/var/lib/gdbm/data," and "/var/lib/gdbm/ctrl." Make install should also take care of this process. Ensure all three directories are owned by "gdbm."
Once that's complete, copy the sections of "/etc/passwd" and "/etc/group" containing any users who should have access to the daemon to "/var/lib/gdbm/ctrl/passwd" and "/var/lib/gdbm/ctrl/group," respectively.
Afterward, start the daemon as gdbm using a command such as "sudo -u gdbm /usr/sbin/gdbmd" or "su -c /usr/sbin/gdbmd gdbm." Keep in mind that the installation doesn't start the daemon automatically, nor does it include a system startup script.
Finally, write an application on the client that replaces the standard gdbm_* calls with rgdbm_* calls. The rgdbm_connect() and rgdbm_disconnect() functions are necessary to begin and end the session, respectively, as outlined in the rgdbm(3) man page.
Overall, Remote Gnu Database Manager is easy to install and use, with clear instructions on how to set it up for SSL. It's also relatively simple to implement in your code, as outlined in the example provided. The latest release adds a generated Debian directory to the package.
The first step is to create a user, "gdbm," on the server machine with home in "/var/lib/gdbm." Typically, this is taken care of by the "make install" function, which utilizes "adduser." However, it's recommended that you check "/etc/passwd" and "/etc/group" to ensure everything is set up correctly.
Next, create directories "/var/lib/gdbm," "/var/lib/gdbm/data," and "/var/lib/gdbm/ctrl." Make install should also take care of this process. Ensure all three directories are owned by "gdbm."
Once that's complete, copy the sections of "/etc/passwd" and "/etc/group" containing any users who should have access to the daemon to "/var/lib/gdbm/ctrl/passwd" and "/var/lib/gdbm/ctrl/group," respectively.
Afterward, start the daemon as gdbm using a command such as "sudo -u gdbm /usr/sbin/gdbmd" or "su -c /usr/sbin/gdbmd gdbm." Keep in mind that the installation doesn't start the daemon automatically, nor does it include a system startup script.
Finally, write an application on the client that replaces the standard gdbm_* calls with rgdbm_* calls. The rgdbm_connect() and rgdbm_disconnect() functions are necessary to begin and end the session, respectively, as outlined in the rgdbm(3) man page.
Overall, Remote Gnu Database Manager is easy to install and use, with clear instructions on how to set it up for SSL. It's also relatively simple to implement in your code, as outlined in the example provided. The latest release adds a generated Debian directory to the package.
What's New
Version 2.1.41: N/A