01-25-2009
upgrade the firmware if necessary. it might be the cause..
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I'm having all kinds of trouble jumpstarting some SS20's.
After hunting around the newsgroups I find that this seems to be a fairly common problem with no real answer.
Here's a brief:
SS20, 50mhz, 256mb blah blah. - Client
E250 blah blah - J/start server.
10/100bt Network.... (4 Replies)
Discussion started by: itsupplies
4 Replies
2. Solaris
hi,
i hv received SUNfire 280R system ........for its initial configuration i want to connect to it through hyperterminal from the windows system..........i hv got one serial port to RJ-45 port converter with the system............can anybody tell me the normal console cable which is used to... (3 Replies)
Discussion started by: girish_shukla
3 Replies
3. Solaris
Hi there
Does anybody know what the biggest capacity disk I can get into a Sunfire 280R
I currently have two 73gb disks , but I need to get these up to the biggest available
Any help would be greatly appreciated (4 Replies)
Discussion started by: hcclnoodles
4 Replies
4. Solaris
Hi,
Could someone please explain it to me how much space in MG or GIG available if i can create another mount point or another slice by looking at this output:
# prtvtoc /dev/rdsk/c1t1d0s0
* /dev/rdsk/c1t1d0s0 partition map
*
* Dimensions:
* 512 bytes/sector
* 424 sectors/track... (2 Replies)
Discussion started by: lamoul
2 Replies
5. Solaris
Hi,
I have to question:
1) when O/S is booting, i see messages:
/dev/rdsk/c1t0d0s5: is logging
/dev/rdsk/c1t0d0s3: is logging
/dev/rdsk/c1t0d0s7: is logging
i partitioned these slices during installation of O/S 5.9. I can access to these mountpoint no problem. But... (3 Replies)
Discussion started by: lamoul
3 Replies
6. Solaris
hi,
i just completed installing O/S 5.9 on Sunfire 280R with O/S 5.9. During installation, i wasn't able to add IP, Default gateway, NDS and netmask because the lan port wasn't not active yet. Now that i have a lan port active, how to add network components onto the system?
I did ifconfig to... (1 Reply)
Discussion started by: lamoul
1 Replies
7. Solaris
Hi,
i just finished installing solaris 5.9 and I'm looking for the tools to tell me if i should update the patches or how to make sure that the current patches are ok?
thanks (2 Replies)
Discussion started by: lamoul
2 Replies
8. Hardware
Hi,
I'm a newbie in the Unix world... :confused:
I own a Sun Sunfire 280R computer with one 750Mhz CPU. I ordered two CPU of 900Mhz to replace it; however in the Service manual from Sun I read that to use 900Mhz CPU i will need to have a OBP of at least version 4.5.16. When I type .version in... (2 Replies)
Discussion started by: Monkey114
2 Replies
9. Hardware
I got the system couple of days back from one of my friend. Last night I turned it on and I noticed that maintenance LED is on. At the same time I added an LCD monitor via VGA and nothing was showing on the screen. Though the system does not have any HDD So not sure if system will even show a BIOS... (3 Replies)
Discussion started by: pgirish007
3 Replies
10. Solaris
Dear all!
I've received 4 servers Sparc T4-2 on a rack, those servers was built in Solaris 11 ZFS bundled. Our Application is not coporated with the Sun 11, so, I must reinstall them.
However, whenever I ran cdrom in "ok prompt> bood cdrom", I received the line "Can not load cdrom". Recheck... (9 Replies)
Discussion started by: trantuananh24hg
9 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)