This module hooks '$SIG{__WARN__}' and converts warnings to the Test::More
manpage's 'fail()' calls. It is designed to be used with 'done_testing',
when you don't need to know the test count in advance.

Just as with the Test::NoWarnings manpage, this does not catch warnings if
other things localize '$SIG{__WARN__}', as this is designed to catch
_unhandled_ warnings.

This package provides a wrapper binary to run smbspool
with the original user ID who submitted a print job.

When printing in a Windows Active Directory (AD) environment
the user 'lp' is not allowed to print in this environment
so that the traditional way to print via smbspool as user 'lp'
would not work.

When Kerberos is used for authentication in an AD environment,
a user gets a so called "ticket" via the display manager
during login at the Gnome or KDE desktop.
When smbspool is run as the original user who submitted
a print job, it can access the ticket of the user that is
needed in an AD environment with Kerberos authentication
to pass the printing data to the SMB printer share.
A precondition is that it runs on the same host where
the user who submitted the print job is logged in.
This means it must be set up on the workstation
for the user who will submit the print jobs and
the user's workstation must send its printing data
directly to the SMB printer share in the AD environment.
It does not work on a separated CUPS server machine
where users who submit print jobs are not logged in.

MySQLTuner is a script written in Perl that will assist you with your MySQL configuration and make recommendations for increased performance and stability. Within seconds, it will display statistics about your MySQL installation and the areas where it can be improved.

It's key to remember that MySQLTuner is a script which can assist you with your server, but it is not the solution to a badly performing MySQL server. The best performance gains come from a thorough review of the queries sent to the server, and an evaluation of the MySQL server itself. A qualified developer in your application's programming or scripting language should be able to work with a MySQL database administrator to find improvements for your server. Once the server and application are optimized well, you may need to consider hardware upgrades to the physical server itself.