07-28-2009
thanks microbot for you effort helping me and i will make this upgrade
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have a Dell Inspiron 4000 that I am using to run Redhat Linux 7.1.
This machine had 128Mb of RAM in it, and I upgraded to 512Mb.
Since this, the PCMCIA cards have disappeared from the system running under Linux, although they still work under windows and the file "/var/lib/pcmcia/stab"... (1 Reply)
Discussion started by: ghoti
1 Replies
2. Solaris
Can someone tell me what the following means? We have a v440 running Solaris 9. What do the patterns actually mean?
May 17 12:12:03 ibasdb02 cediag: Revision: 1.78 @ 2005/02/11 15:5
:29 UTC
May 17 12:12:03 ibasdb02 cediag: Analysed System: SunOS 5.9 with
UP 117171-17 (MPR active)
May 17... (5 Replies)
Discussion started by: hshapiro
5 Replies
3. UNIX for Advanced & Expert Users
I have worked with Qlogic (Sun) fiber cards a lot and with Emulex fiber cards only a little. Here is the scenario: I have a Sun 490 with 3 Emulex cards in it. A pair are for the 6120 array that is attached, the other is a direct attach so our SAN for Veritas Netbackup to back up the system.I... (0 Replies)
Discussion started by: lm_admin_dh
0 Replies
4. Solaris
Dear All
I would Like to know that if suppose c1t0d0 is of 72 gb hard disk and system boot from this hard disk and c1t1d0 is of 147gb hard disk. Can we implement hardware raid (Mirror) between these two hard disks of different capacity if raid crontroller is present in the server
Kind regards (4 Replies)
Discussion started by: girish.batra
4 Replies
5. Solaris
Hi
I am right now facing a strange hardware problem. System get booted with the following error:
Fatal Error Reset
CPU 0000.0000.0000.0003 AFSR 0100.0000.0000.0000 SCE
AFAR 0000.07c6.0000.1000
SC Alert: Host System has Reset
It happen 4 or 5 times and get the same error every time.I... (8 Replies)
Discussion started by: girish.batra
8 Replies
6. Linux
Hey guys how to do diagnose Linux for hardware problems/issues. This is a general question for all common hardware components under Linux server. (1 Reply)
Discussion started by: sbn
1 Replies
7. Solaris
Hey guys how to do diagnose solaris for hardware problems/issues. This is a general question for all common hardware components under solaris server. (4 Replies)
Discussion started by: sbn
4 Replies
8. HP-UX
Hey guys how to do diagnose HP-UX for hardware problems/issues. This is a general question for all common hardware components under HP-UX server. (4 Replies)
Discussion started by: sbn
4 Replies
9. Solaris
First of all it's shut down 60 second after power on and write on console :
SC Alert: Correct SCC not replaced - shutting managed system down!
This is cured by moving out battery from ALOM card.
Now server start to loop during the testing.
That's on the console:
>@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies
10. Solaris
Hi folk,
I have this hardware faunty message, but dont know which hardware is this ? can you guide me ?
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies
LEARN ABOUT PLAN9
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)