Use "oslevel -qs" (q=query) to see all the oslevels your system knows about. Hopefully, the TL8 is at the top of your list.
Then use "oslevel -sl 7100-01-04-1216" (l=lacking) with the version number being the level you are trying to get to and it should tell you which filesets are down leveled. You can then focus your efforts on finding later versions of them and getting them updated.
Hi guys
I have joined a new department and one of my tasks is to investigate the feasibility of upgrading our current AIX v 4.3 to V5.3.
I do not know anything about AIX and any actual work will be done by an outside consultant until such time as I have built up my own knowledge.
The system we... (3 Replies)
Hello everyone, I have to do a ML upgrade on AIX 5.2 from 01 to 09
this is the first time iam going to do it.
are there any command i have to keep in mind??
thanks! (1 Reply)
I have an IBM P520 that I need to upgrade from 5.2 to 5.3. My background in Unix is from 15 years ago so I don't remember much. IBM documentation is hard to find. Any help would be appreciated. (1 Reply)
dear frnds,
i m very new linux environment & is looking to deploy squid proxy server using Fedora 9.
but i do not know anything abt all this. i have installed fedora in default mode & it has squid already installed. now i want to upgrade the squid to current version.
i tried to use yum to... (2 Replies)
Hello Folks,
i am facing some weired issues.
case is like this :-
initially i was on AIX 5.3
i have installed filesets related to my application and those were in APPLY state.(COMMIT is set as NO)
Then i have taken lslpp -l| grep -i <apps name>
in that i confirmed whether the filesets are... (1 Reply)
i upgrade aix ml 5.3.2.1 to 5.3.2.2 but when running commnd #oslevel -r
shows out put, again 5.3.2.1-- where should i chek???
2-can any one tell me when mknfs command run which files get updated?? (2 Replies)
dears
i am trying to upgrade the TL from TL7 to TL8 and i facing this issue AIX6.1
<< End of Success Section >>
+-----------------------------------------------------------------------------+
BUILDDATE Verification ...... (2 Replies)
Hi
I'm trying to upgrade the AIX TL on my test LPAR.
current os level is "7100-01-06-1241"
Planning to upgrade it to latest TL. "7100-02-03-1334"
1) Downloaded the TL files from fix central
Selected "7100-02-03-1334" --> requisite "7100-02-00-1241" ==> Downloaded both
2) backedup... (9 Replies)
Discussion started by: System Admin 77
9 Replies
LEARN ABOUT XFREE86
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 ALSOdebhelper(7)AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)