01-11-2019
Hi,
In that case, I'd just be tempted to write your own "start|stop|restart" and put it into /etc/init.d with the Start and Kill in /etc/rc3.d. Check this
thread out - I know it's AIX but the example is valid.
Regards
Gull04
Last edited by gull04; 01-11-2019 at 04:47 AM..
Reason: More Info
This User Gave Thanks to gull04 For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
on Solaris 5.8 I've installed SunMgtCenter to get the time agent;
it's under /opt/SUNWsymon/sbin/es-start -a
it's in ps -ef | grep agent
...but it doesn't work; the machine is always in alarm cause the time is different of the clock server;
is it clear enough ?
tks
cc (0 Replies)
Discussion started by: Carmen123
0 Replies
2. Solaris
Hi,
I am trying to apply the steps in the below link:
http://manageengine.adventnet.com/products/applications_manager/help/appendix/snmp-agent-discovery.html#solaris
but I couldn't continue with the step number 2 ... what is the path of C compiler.
export PATH=<gcc path>:$PATH
... (3 Replies)
Discussion started by: adel8483
3 Replies
3. Solaris
Hi ,
Please help me to install Tripwire agent in one of my Solaris 5.9 server.
I have a zipped copy of the agent file in my local drive. When trying to ftping the file from local drive to the server its showing error as " cannot copy the files" Please help me to solve this issue.
... (2 Replies)
Discussion started by: Renjesh
2 Replies
4. Infrastructure Monitoring
Tim Bass
03-20-2009 07:02 AM
Source... (0 Replies)
Discussion started by: Linux Bot
0 Replies
5. Infrastructure Monitoring
Tim Bass
03-23-2009 03:45 PM
Source... (0 Replies)
Discussion started by: Linux Bot
0 Replies
6. AIX
Hi all. I hope someone could give me a hand on installing Backup Exec agent on AIX machine :(
Agent:
OS: AIX 5.3
Hostname: DB-HN-SRV02
IP: 10.1.4.64
Backup server:
OS: Windows Server 2003
Hostname: backup-srv
IP: 10.1.5.51
I download "Legacy Unix agent.tar", untar, then run file... (0 Replies)
Discussion started by: bsddaemon
0 Replies
7. Infrastructure Monitoring
Anyone has a step by step guide in installing Zabbix on Solaris 10? I'm new in this, and every help is appreciated. :) (4 Replies)
Discussion started by: jolie
4 Replies
8. Solaris
I am trying to build a Sun Ultra 10 with solaris 10. This computer is one of a collection that was donated to the non-profic company I work for. All media was wiped before I recieved them, so I am starting from stratch.
I downloaded the Solaris 10 ISO and burned a DVD. The computer came with a... (4 Replies)
Discussion started by: gwillhight
4 Replies
9. Solaris
hi, dear all
I get a problem "VCS ERROR V-16-2-13077 " on VCS 4.1 for Solaris 10.
I can not offline the host2 when the raid is bad.
I don't know the reason and how to offline host2 and switch to host1.
please help me, thank you!
the message of engine_A.log is :
... (2 Replies)
Discussion started by: ForgetChen
2 Replies
10. Solaris
Client has got a few machines with logical domains on.
But I can't see the the ovs-agent service?
Quite possibly I guess this has been set up with just logical domains. With no agent.
Do you need to use the agent only if planning to manage with OV Manager? (6 Replies)
Discussion started by: psychocandy
6 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)