Hi all
A couple of new M5000 servers will be arriving soon and I need to work out how to configure the underlying domains.
It will come with 4 x CPUS, 32 Gb of memory, 4 x HD, 2 x IOtrays.
Reading the XSCF manual, I can configure the item into 2 domains, something about uni / quad xsb.... (9 Replies)
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)
Hello
I need to upgrade our Solaris 10 OS Update 9 as we are not ready for u10 yet.
I asked MOS for Update 9 which they supplied and I've downloaded.
The thing is, it's in a zip file which I have extracted on the server but all the docs I have seen regarding lu, talking iso, images and... (9 Replies)
Hi,
I've configured this Sun M5000 to use two system domains (added a second domain to it). The following is the info about the settings. The showdevices command can't show devices on domain 1 because Solaris is not loaded on it yet.
My question: How can I confirm the hardware devices such as... (5 Replies)
Hi,
I would appreciate some help.
I remotely access, across a VPN, an M5000 and when I connect to the XSCF I can then access the OS using console -d0 and then I can get to the console.
The problem I have is that I need to run something which will take many hours and I can't run it in the... (6 Replies)
I am upgrading Solaris-9 Update-7 to Solaris-9 Update-9 through live upgrade. I am able to create another boot environment and have OS DVD inside server. But i am confused for, what command/path should I give for luupgrade.
OS DVD is mounted on /mnt
Boot environments are Solaris9old (Active now)... (2 Replies)
Hi All,
Is it possible to use external san disk for creating alternate boot environment and boot from it.My root disk is about 70 gb and i want to use external san disk for 272gb to create alternate boot environment.If this is possible can you please redirect me some good documents, i had... (1 Reply)
Trying to update my M5000 firmware. trying to mount my USB to upload firmware and getting the following message.
XSCF> getflashimage -v file:///media/usb_msd/FFXCP1115.tar.gz
Free space: 97MB
Making sure mount point is clear
umount: /media/usb_msd is not mounted (according to mtab)
Trying... (2 Replies)
I am new to AIX administration and am trying to upgrade my current TL from 6100-05 to 6100-07 , I had a look at the fix central and I have downloaded one which says TL 6100-07-00-1140 and other which says service pack 6100-07-05-1228. I have two test machines and I have applied directly... (0 Replies)
I took over an M5000 and have a jumper server with a nic to connect to the console IP of an M5000. access via ssh user@ip.
it was working fine, another person can connect remotely on the subnet, but when I ssh,it just hangs and then times out.
so my question is,
any ideas of what I might... (4 Replies)
Discussion started by: rrodgers
4 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)