cpbandwd. Each of these older processes performed very similar functions. The common functionality has been merged into a single process. As a result, the system resource requirements are reduced.
jailmanager(new in 11.38)
eximstatsare removed with the upgrade to
TailWatch. You can control which TailWatch drivers are enabled in the Service Manager screen in WHM (Home >> Service Configuration >> Service Manager). Once the upgrade to TailWatch is complete, the older scripts, such as
/usr/local/cpanel/bin/eximstats, will no longer be used. These scripts will eventually be removed at a later update. An attempt to start the older process will result in failure, and a message will inform the user to use TailWatch instead.
chkservdis the driver used to determine if a process is online and whether the process needs to be restarted. You can decide which services are monitored via the Home >> Service Configuration >> Service Manager interface. By default,
chkservdchecks each service every five minutes to determine if the server is online. This setting, along with other
chkservdconfiguration options, can be modified in WHM via Home >> Server Configuration>> Tweak Settings >> System .
The Tweak Settings screen in WHM.
chkservdlog file contains the results from the check. This file can be found at
/var/log/chkservd.logIf a service is online,
chkservdwill move onto the next service. If a service is offline,
chkservdwill attempt to restart the service via the cPanel restart scripts located in:
clamd. Remember: In the example below,
clamdcan be replaced with any other service.
rm -f /var/run/chkservd/clamd
rm -f /etc/chkserv.d/clamd
chkservdconfiguration file with your preferred text editor. You may need to remove the line for
chkservdconfiguration file can be found at:
chkservd, the other drivers do not have their own log files or configuration. Information for these drivers are logged to the main
tailwatchdlog file at
/usr/local/cpanel/bin/tailwatchd. You can obtain a full list of flags is obtainable via the
/usr/local/cpanel/bin/tailwatchd - Driver based real time log processing
--help This screen--version Show version of Cpanel::TailWatch--version=long Same as --version but also include active driver modules versioninformation also.--status Status information--status=long Same as --status but also include information about the PID if its running--stop Stop current tailwatch daemon--start Start tailwatch daemon--restart Start tailwatch daemon, stopping it first if necessary--trace log the first 10,000 lines the drivers collectively process--trace=n log the first 'n' lines the drivers collectively processTrace only takes effect on --[re]start.--start --trace (equivalent to --start --trace=10000)--restart --trace='perl -e 'print 12+3-4+5+67+8+9;''--start --trace=1729--status --trace (--trace has no effect here)--debug This tells all driver's to log() debug messages.Debug only takes effect in --[re]start. Typically the message should be prefaced with‘[debug]’ and are about processed lines that result in an entry of some sort--perldoc This shows the POD for Cpanel::TailWatch
/usr/local/cpanel/Cpanel/TailWatch. Once the drivers are in place, you can restart TailWatch to load the new drivers; this action will provide the driver's functionality.