08-24-2002
My suggestion would be to first rebuild the system using the original OS on the new hardware..... and then after that is up and running well, consider an OS upgrade.
It is really 'too much work' to try to mend and upgrade a crashed app AND OS, all at once.... baby steps..... first simply rebuild the app without changing the OS version.
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
1) how is a hot backup performed.
i am thinking it does 1 of 2 things.
1) it exports the db and then you backup the exported files.
OR
2) you just backup the files on disk as teh db is running.
i dont need to know HOW it is done. but just the basic concept of a hotbackup. i cant find it... (1 Reply)
Discussion started by: Optimus_P
1 Replies
2. Programming
Hi-
I need the cpp call that will tell me the full path to the app I'm running in. For example, I'm running in a loaded library for either mozilla or firefox, but would like to know the full path to the executable
/usr/bin/firefox
/usr/bin/mozilla
/usr/local/firefox1_5
etc...
(For... (4 Replies)
Discussion started by: erwinfletch
4 Replies
3. Programming
Hello!
I just programmed a very simple app, it's function is to report every minute the state of the memory and cpu and put it to and xml.
All this stuff is working ok since I'm logged in into the machine, but i want it to run as a service, how can I do that??
P.S: Any one knows how can I... (1 Reply)
Discussion started by: ncatdesigner
1 Replies
4. High Performance Computing
Here are steps for installing the Solaris 10 11/06 OS, Solaris Cluster (formerly Sun Cluster) 3.2 software, QFS 4.5, and Oracle 10gR2 RAC. Also provided are instructions on how to configure QFS and Solaris Volume Manager for use with Oracle 10gR2 RAC.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
5. Windows & DOS: Issues & Discussions
Hi.
I was, not too long ago, an OS X home user. One of the things I remember from using the Apple-installed Terminal is: whenever an executable that took more than a split second to do its thing was running, its name would appear in the title bar in a way similar to "Terminal: ssh" or "Terminal:... (0 Replies)
Discussion started by: SilversleevesX
0 Replies
6. AIX
Hi,
A quick question. If I build an application on AIX 6.1 TL3 using XL C/C++ 8.0 and Oracle 10g, can I then take those binaries and run them on AIX 5.3 and previous?
Regards
Kevin (3 Replies)
Discussion started by: KevB
3 Replies
7. Solaris
what is the command to see which database ie..oracle in running on solaris 10 (2 Replies)
Discussion started by: tv.praveenkumar
2 Replies
LEARN ABOUT CENTOS
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)