/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Unitrends Protect

Disable/Enable Upstart services for Linux clients

SUMMARY

This article explains how to disable (and re-enable) the bpinetd and mynotify Upstart services for Linux clients.

ISSUE

After installing the Unitrends agent on a Linux client which uses the Upstart init system, the bpinetd and mynotify services will automatically start at system boot. In most cases, it will never be necessary to disable these services. However, if you do need to disable them, this article explains how. It also provides instructions for enabling the services after they have been disabled. While these services are disabled, backups will not run for the Linux client.

Note: Not all Linux systems use Upstart. If the files /etc/init/bpinetd.conf and /etc/init/mynotify.conf do not exist, then this article is not applicable.

Disable Upstart services

Disabling the services is a two part process. First, you must create an override file. Then stop the services manually.

Create an override file

Create an override file for the service to be disabled.

# echo manual > /etc/init/bpinetd.override

and/or

# echo manual > /etc/init/mynotify.override

Stop the service

Stop the service you wish to disable.

# service bpinetd stop

and/or

# service mynotify stop

The services will remain disabled until manually started.

Restore Upstart services

To restore the services to their original behavior, remove the override files and start the services manually.

Remove the override file

# rm /etc/init/bpinetd.override

and/or

# rm /etc/init/mynotify.override

Start the service

# service bpinetd start

and/or

# service mynotify start