Posts

Table 1: Recommended system swap space in Fedora 28 documentation {.wp-block-heading} Amount of system RAM Recommended swap space Recommended swap with hibernation less than 2 GB 2 times the amount of RAM 3 times the amount of RAM 2 GB – 8 GB Equal to the amount of RAM 2 times the amount of RAM 8 GB – 64 GB 0.5 times the amount of RAM 1.5 times the amount of RAM more than 64 GB workload dependent hibernation not recommended Table 2: Recommended system swap space per the author {.wp-block-heading} Amount of RAM Recommended swap space ≤ 2GB 2X RAM 2GB – 8GB = RAM >8GB 8GB

Adminer (formerly phpMinAdmin) is a full-featured database management tool written in PHP. Conversely to phpMyAdmin, it consists of a single file ready to deploy to the target server. Adminer is available for MySQL, MariaDB, PostgreSQL, SQLite, MS SQL, Oracle, Firebird, SimpleDB, Elasticsearch, and MongoDB. install script sudo mkdir /usr/share/adminer sudo wget "http://www.adminer.org/latest.php" -O /usr/share/adminer/latest.php sudo ln -s /usr/share/adminer/latest.php /usr/share/adminer/adminer.php echo "Alias /adminer.php /usr/share/adminer/adminer.php" | sudo tee /etc/apache2/conf-available/adminer.conf sudo a2enconf adminer.conf # restart apache/httpd

When using Git for version control, many people use GitHub as a place to hold remote repositories and push their repositories there. I recently started using BitBucket also and wanted to be able to simultaneously update my GitHub and BitBucket repositories when changes were made. To begin, rename your current remote (most likely named origin) to a different name. I’d rename this to the name of the service you are using, such as Github or bitbucket. ...

Add --max_allowed_packet=512M to your mysqldump command. Or add max_allowed_packet=512M to [mysqldump] the section of your my.cnf Note: it will not work if it is not under the [mysqldump] section…

To get updated content from the feeds you need to run the following scripts (in this order) on a daily base crontab -e 0 1 * * * /usr/sbin/greenbone-nvt-sync &> /dev/null 0 2 * * * /usr/sbin/greenbone-scapdata-sync &> /dev/null 0 3 * * * /usr/sbin/greenbone-certdata-sync &> /dev/null If there is any issue during the sync the scripts should give you additional info.