01-19-2009
#. will not drop you into the OBP. it will put you into the system controller.
look like: sc>
what i'm confused about is why you want to be at the OBP when you want to start the installation? after what DN2 has posted, and your post, the installation has started which was what you wanted from the start? am i wrong on this?
9 More Discussions You Might Find Interesting
1. Solaris
Hi all,
I have just replaced the HDD on a Ultra 5 Spark machine, now I need to reinstall Solaris 9.
The problem is: how do I get to the OK prompt without a Sun keyboard in order to boot from CD?
At moment when I power on the machine I get the following error:
Timeout Waiting for ARP/RARP... (13 Replies)
Discussion started by: sspirito
13 Replies
2. Solaris
Hi,
I have Sun SPARC Enterprise T5140 and I can't access it via serial port using preconfigured administrator account, as described in Sun Integrated Lights Out Manager 2.0 User's Guide: I'm always receive "Login incorrect" message. I'm really confused! Does anyone experience such circumstances?... (12 Replies)
Discussion started by: Sapfeer
12 Replies
3. Solaris
What is the serial port on the T5140 used for. (4 Replies)
Discussion started by: pgsanders
4 Replies
4. Solaris
Hi,
I need configure this server for two zones (oracle and glassfish). Server has 2CPU 8cores = 128vcpu and 16 GB RAM.
I am interested in mainly the division of the processor and memory.
What was the configuration that best for Oracle zones? (4 Replies)
Discussion started by: bieszczaders
4 Replies
5. Solaris
Hi all,
I use latest bind 9.6.1, brand-new T5140 Sun Server, 10u8 Solaris OS, Mar-2010 OS patch to configure a caching dns server.
But bind always hang up when process/cache is reaching to 500 Mb ( Though 'prstat -a' check )
Can anyone help me a solution for this problem, i will greatly... (0 Replies)
Discussion started by: tien86
0 Replies
6. Solaris
Hi, I've got an issue here: After I logon to the xscf prompt of this Sun M5000 and did 'XSCF> version -c xcp', the xscf prompt disappeared. I can't get it back and can't log out.
exit
rebootxscf
logout
#.
#>
#>
~#
~#
exit
sendbreak
exit
I tried to set the Mode Switch to the service... (3 Replies)
Discussion started by: aixlover
3 Replies
7. Solaris
I've been busy and fell behind on Sun/Oracle. Forgive me if too basic. I welcome brief, cryptic, or advanced replies. I also welcome noobie information since I may have no clue what's up at the moment.
Problem statement:
I inherited a computer to set up. I would rather not figure out 8 months... (1 Reply)
Discussion started by: Nevyn
1 Replies
8. Solaris
Hi All,
We have a T5140 server which has 128 threads in total. Is it possible to reduce the number of threads per core through some configuration changes? I am sorry for being so naive but I am one on this.
Why would I like to do this? Unfortunately we have this for an Oracle Database Server... (6 Replies)
Discussion started by: VENKITACHALAMS8
6 Replies
9. Solaris
I am having a problem when booting my Sun V445 machine with Solaris 10 installed on it. Machine hangs at boot at following step :
0>Copyright 2007 Sun Microsystems, Inc. All rights reserved
0>OBP->POST Call with %o0=00000800.01014000.
0>Diag level set to MAX.
0>Verbosity level set to... (21 Replies)
Discussion started by: usmanijaz101
21 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)