05-15-2002
10 More Discussions You Might Find Interesting
1. Solaris
required Solaris 5.10 Kernel patch 137111-03
required Solaris 5.10 Fibre Channel Device Driver patch 125184-08
I want to know about the descriptions and what the patches will do. I searched www.sun.com (patches/updates) but don't see I am looking for. (1 Reply)
Discussion started by: Y4Net
1 Replies
2. AIX
Hello, I recently did an update from 5300-0-0 to 5300-05-06. When I run lppchk -v I get the following errors:
# lppchk -v
lppchk: The following filesets need to be installed or corrected to bring
the system to a consistent state:
invscout.rte 2.1.0.0 (not... (4 Replies)
Discussion started by: dkranes
4 Replies
3. AIX
Hello. Im attempting to install Oracle 11g, but my current AIX is a bit too old. Oracle 11g require TV 5300-05-06, and my current AIX TV is:
% oslevel -s
5300-05-00
So what would be the best way to update TV? Thanks. (6 Replies)
Discussion started by: bsddaemon
6 Replies
4. AIX
Hello
I update one lpar from TL03 to TL06 reboot and check with lppchk -v, errpt and everything looks fine then I commit my fileset and I update to TL08-04.
The installation was ok. I reboot my machine again check with lppchk -v and errpt and its ok, but when I type oslevel -s I get this... (5 Replies)
Discussion started by: lo-lp-kl
5 Replies
5. Solaris
Hi all first post here.
quick question what Solaris 10 update level included this utility?
I have a bunch of Sun boxes at varying levels of Solaris 10 some have it some do not.
When I do my install I take the full option for the packages to install on all the systems.
thanks in advance... Mike (4 Replies)
Discussion started by: mike_243us
4 Replies
6. AIX
Steps to upgrade AIX TL ( technology Level ) / Maintenance Level in AIX ( including Firmware HMC VIOS )
This article or post covers upgrades for
- Hardware Management Console ( HMC )
- Firmware ( also known as microcode )
- VIO ( Virtual I/O Server = PowerVM )
- AIX Version, Technology... (2 Replies)
Discussion started by: filosophizer
2 Replies
7. Solaris
Hi All,
I am planning to do the Solaris level upgrade from "Solaris 10 1/06 s10s_u1wos_19a" to "Solaris 10 10/09 s10s_u8wos_08a" with 7 Non-global zones on it.....
I have done Level upgrade for Solaris 10 boxes without Non-global zones.....
Can any one let me know, whether it is possible... (8 Replies)
Discussion started by: indradev
8 Replies
8. AIX
I'm SO confused about the question of whether I can or cannot update an lpp_source with a bunch of patches. Someone I know who I think knows a lot about AIX and NIM says I should never do this. But I'm looking at the Redbook "NIM from A to Z in AIX 5L", which seems to describe exactly how to do it,... (10 Replies)
Discussion started by: tgphelps
10 Replies
9. AIX
As i have updated a lot of HACMP-nodes lately the question arises how to do it with minimal downtime. Of course it is easily possible to have a downtime and do the version update during this. In the best of worlds you always get the downtime you need - unfortunately we have yet to find this best of... (4 Replies)
Discussion started by: bakunin
4 Replies
10. AIX
Hello,
I was trying to upgrade TL on a lab server (test box). I did worked on (few) these type of SP and TL updates in the recent past. I saw the below message for the first time on server.
current OS level : 7100-03-01-1341
downloaded the newest/recent fix pack from fix central as... (3 Replies)
Discussion started by: system.engineer
3 Replies
LEARN ABOUT FREEBSD
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)