02-23-2009
On the two most prevalent package management systems for Linux (deb and rpm) that information isn't really accessible, but depends on what the pre-/postinstall scripts embedded in the package do and how the maintainer wrote those.
As for downtime: a typical Apache upgrade for me never resulted in more that 30 seconds downtime (which was on a P90, long ago). Since an upgrade should be done between business hours anyways (in case somethings goes terribly wrong) a blip of about 5 minutes shouldn't do too much of an impact on business. If it would I suggest investing in redundancy and update only one node at a time.
8 More Discussions You Might Find Interesting
1. AIX
given any specific fix, how can I determine if the machine will require a reboot? (I don't have a window for downtime)
obvious fix's to the kernel / lvm will require a reboot ... bos.rte files etc...
is there a tool or command that I am able to run against a specific IY that will inform me... (4 Replies)
Discussion started by: A Stewart
4 Replies
2. Solaris
Hi - How can I determine the time my system was last booted when my "wtmp" file is broken? (It is being cleaned out incorrectly, I'mm working on that issue)
ie
uptime shows invalid details and who -b shows "nothing at all"
is there a shutdown log somewhere that may indicat the last re-boot? (3 Replies)
Discussion started by: Andrek
3 Replies
3. Solaris
Hi Folks,
Is there anyway I can determine the package set (or SIP) that a package belongs to. It doesn't seem that pkginfo does it?? I'm trying to remove a whole lot of unecessary packages, and it would be far more convenient if I could remove whole sets at a time instead of indivdual packages.... (0 Replies)
Discussion started by: brizrobbo
0 Replies
4. Linux
have following package installed
rpm -qa |grep ADMIN
It will give the following package installed:
ADMIN-4.0.0.1
Now I will upgrade the ADMIN package using the following command.
rpm --upgrade ADMIN-4.1.0.1
It will upgrade the ADMIN packagge to ADMIN-4.1.0.1
Now I want that... (0 Replies)
Discussion started by: amitpansuria
0 Replies
5. UNIX for Dummies Questions & Answers
Dear linux-unix users,
I hope that one of you will be able to help me.
How can I determine to which package a file or binary belongs to.
With solaris/linux package managers you can easely determine this but i cant find the way how to do this on tru64.
Any help would greatly be appreciated.... (0 Replies)
Discussion started by: Crazy_lenny
0 Replies
6. UNIX for Advanced & Expert Users
Friends,
Please let meknow, How we can find the dependancies of .dstream package & .rpm package before installation ?
For AIX, We can use the inutoc . command to create the .toc file for the bff package, What about Solaris & Linux ? (0 Replies)
Discussion started by: yb4779
0 Replies
7. UNIX for Dummies Questions & Answers
Hello,
i have downloaded an rpm package "hadoop-0.20.205.0-1.amd64.rpm"
in /usr/local/ directory.
I'm trying to install the rpm package in a new path/location (/usr/local/hadoop-0.20.205), but i can't.
I did:
1st try: Didn't work
sudo rpm -i --prefix=/usr/local/hadoop-0.20.205... (1 Reply)
Discussion started by: g_p
1 Replies
8. Emergency UNIX and Linux Support
Hello,
i have installed a package by using the command
sudo rpm -i filepackage.rpm
package filepackage is already installed
when i try to remove it, i get an error saying "is not installed":
sudo rpm -e filepackage.rpm
error: package filepackage is not installed
How can... (4 Replies)
Discussion started by: g_p
4 Replies
LEARN ABOUT OSF1
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)
NAME
dh_systemd_start - start/stop/restart systemd unit files
SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
sysv init script is available.
As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because
invoke-rc.d performs the stop/start/restart in that case.
OPTIONS
--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).
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.
Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)