Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support Different OS Kernel Update Frequency Post 302560306 by Peasant on Thursday 29th of September 2011 11:55:39 AM
Old 09-29-2011
You will need a cluster for such actions.

Think about it, you upgrade and something goes wrong ?
Your service will be down during the time you are restoring backup.

With cluster and proper backup, you can safely upgrade with service being up all the time (this to some extent depends of the service itself.)
This User Gave Thanks to Peasant For This Post:

7 More Discussions You Might Find Interesting

1. Linux

kernel patch update how to

Hi All, I need to update my redhatas4 kernel with kernel-2.6.9-67.0.20.EL.src.rpm. When I run this # rpm -ivh kernel-2.6.9-67.0.20.EL.src.rpm warning: user brewbuilder does not exist - using root warning: group brewbuilder does not exist - using root warning: user brewbuilder does... (2 Replies)
Discussion started by: itik
2 Replies

2. Solaris

Solaris kernel Update

Hi All, I am installing kernel Update 3.0 in my Solaris servers. It actually installs most of the patches in this update , but for some packages it is not installing. It is saying ... Version of package SUNWcakr from directory SUNWcakr.us in patch 137137-09 differs from the package... (7 Replies)
Discussion started by: jegaraman
7 Replies

3. Solaris

kernel update

Hi I am installeing Solaris Kernel update in my solaris Server. The Solaris Kernel update skipps the patch 120011-14. saying that it had already been installed. But it is not found in /var/sadm/patch directory where all the patches will be there. And also i could not install other... (11 Replies)
Discussion started by: jegaraman
11 Replies

4. Red Hat

Kernel Update

1. Where do i obtain new kernels in ".rpm" format to update my RHEL5? is it only available to RHN subscribers? 2. i downloaded latest kernel (linux- from kernel.org. #tar -xjvf linux- after this i have a directory with lots of stuff in there. how do... (2 Replies)
Discussion started by: dplinux
2 Replies

5. Solaris

how to update the kernel patches in solaris 10

tell me the step by step procedure for updating the kernel patches in solaris 10. (1 Reply)
Discussion started by: tv.praveenkumar
1 Replies

6. Red Hat

Linux kernel update

Dear all, I have some linux servers in my prod environment. For two years i have not done any kernel updates or required patches ...should i have to this activity. My kernel version is 2.6.18-164.el5xen and linux release is release 5.4 (Tikanga). And reboot also not done for 2 years is... (2 Replies)
Discussion started by: jegaraman
2 Replies

7. UNIX for Dummies Questions & Answers

How to check NTP update frequency?

Hi i want know to how to check NTP update frequency for a server? what should be its ideal value or range ? also, i have configure one switch and on gui i can see NTP update frequency value is 1440. also no idea what should be its ideal value i am not sure if this is correct or not .... (1 Reply)
Discussion started by: scriptor
1 Replies
DH_INSTALLSYSTEMD(1)                                                 Debhelper                                                DH_INSTALLSYSTEMD(1)

dh_installsystemd - install systemd unit files SYNOPSIS
dh_installsystemd [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [--no-enable] [--name=name] [unitfile...] DESCRIPTION
dh_installsystemd is a debhelper program that is responsible for enabling, disabling, starting, stopping and restarting systemd unit files. In the simple case, it finds all unit files installed by a package (e.g. bacula-fd.service) and enables them. It is not necessary that the machine actually runs systemd during package installation time, enabling happens on all machines in order to be able to switch from sysvinit to systemd and back. For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_installsystemd quota.service and dh_installsystemd --name=quotarpc quotarpc.service. FILES
debian/package.service, debian/package@.service If this exists, it is installed into lib/systemd/system/package.service (or lib/systemd/system/package@.service) in the package build directory. debian/package.tmpfile If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is currently only used by systemd.) debian/package.target, debian/package@.target If this exists, it is installed into lib/systemd/system/package.target (or lib/systemd/system/package@.target) in the package build directory. debian/package.socket, debian/package@.socket If this exists, it is installed into lib/systemd/system/package.socket (or lib/systemd/system/package@.socket) in the package build directory. debian/package.mount If this exists, it is installed into lib/systemd/system/package.mount in the package build directory. debian/package.path, debian/package@.path If this exists, it is installed into lib/systemd/system/package.path (or lib/systemd/system/package@.path) in the package build directory. debian/package.timer, debian/package@.timer If this exists, it is installed into lib/systemd/system/package.timer (or lib/systemd/system/package@.timer) in the package build directory. OPTIONS
--no-enable Disable the service(s) on purge, but do not enable them on install. Note that this option does not affect whether the services are started. Please remember to also use --no-start if the service should not be started. --name=name Install the service file as name.service instead of the default filename, which is the package.service. When this parameter is used, dh_installsystemd looks for and installs files named debian/package.name.service instead of the usual debian/package.service. Moreover, maintainer scripts are only generated for units that match the given name. --restart-after-upgrade Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10. In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst. This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon will not get confused by the package being upgraded while it's running before using this option. --no-restart-after-upgrade Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to be stopped in the prerm script and started again in the postinst script. -r, --no-stop-on-upgrade, --no-restart-on-upgrade Do not stop service on upgrade. --no-start Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a corresponding init script). Note that this option does not affect whether the services are enabled. Please remember to also use --no-enable if the services should not be enabled. NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments). Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. SEE ALSO
debhelper(7) AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org 11.1.6ubuntu2 2018-05-10 DH_INSTALLSYSTEMD(1)

Featured Tech Videos

All times are GMT -4. The time now is 04:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy