We are proud to announce that ServaxNet, LLC is now a BBB Accredited Business. This is just another way to show our commitment of honesty, trust, and ethical business practices to our clients.
To check our record at the BBB, please click here.
We thank you for being the most important part of ServaxNet and providing us with your continued support!
Since Kayako Fusion v4 has been released by Kayako, we’ve had to re-engineer a new LoginShare module.
Like the last one, this LoginShare module will support username or email-based authentication and will allow single-login access credentials to your SPBAS and Kayako installations.
There is no working LoginShare plugin for SPBAS and Kayako right now, so we’ve developed our own based on the official LoginShare plugin for PHP Audit. This plugin allows a client to use a single login between your SPBAS and Kayako Helpdesk installations.
The plugin supports email or username authentication, and will automatically update the user if the email used in SPBAS already exists on your Kayako installation.
Apparently new stock installations of cPanel and ClamAVConnector from “Manage Plugins” fail with the default preferences.
How can you tell if you have a failed installation? By checking if freshclam exists on the server:
root@test [~]# freshclam -bash: freshclam: command not found
We had an issue where a server would not be rejecting mail from IP’s listed at zen.spamhaus.org, and found this pretty interesting:
Check what DNS resolvers you are using: If you are using a free “open DNS resolver” service such as Google Public DNS or Level3′s public DNS servers to resolve your DNSBL requests, in most cases you will receive a “not listed” (NXDOMAIN) reply from Spamhaus’ public DNSBL servers. Please use your own DNS servers when doing DNSBL queries to Spamhaus.
A RAM disk or RAM drive is a block of RAM (primary storage or volatile memory) that a computer’s software is treating as if the memory were a disk drive (secondary storage). It is sometimes referred to as a “virtual RAM drive” or “software RAM drive” to distinguish it from a “hardware RAM drive” that uses separate hardware containing RAM, which is a type of solid-state drive.
For more info: http://en.wikipedia.org/wiki/RAM_disk
With that out of the way, how is this actually useful? Recently we’ve been in a situation where we had a machine with CentOS 5.x 32bit, and MySQL was causing loads up to “load average: 50.55, 49.58, 48.62″. The reason for this? CentOS 32-bit systems can not fully utilize >2 GB for MySQL, which resulted in a high created_tmp_disk_tables from MySQL. Therefore, it was constantly writing to disk for it’s operations – and therefore resulting in high I/O and bottle necking the system.