07-04-2007
For checking which services are stopped and why, use 'svcs -x -v'. This will tell you the status of your telnet/ftp services, and in your case, also why they have stopped.
8 More Discussions You Might Find Interesting
1. Cybersecurity
Our systems group is asking if it would be Ok to turn off certain services due to potention security risks. The following are being contemplated.
Service
chargen
daytime
discard
dtspcd
echo
exec
finger
fs
gssd
in.comsat
kcms_server
ktkt_warnd
login
name
rpc.cmsd
rpc.metad... (4 Replies)
Discussion started by: BCarlson
4 Replies
2. Solaris
I want to add auto startup and shutdown script to Solaris 10's legacy services as they run in Solaris 9 or in Linux.
To make this work, I created the crontrol script in /etc/init.d and then link it to /etc/rc0.d and /etc/rc2.d directories. rc0.d is for shutdown and rc2.d is for srat. After I... (15 Replies)
Discussion started by: duke0001
15 Replies
3. Solaris
I've installed Solaris 10 (05-08) on a SPARC platform
During the installation I was prompted with the question below. I selected yes to enable remote services.
Does anyone know what services this option enables?
- Enabling remote services ----------------------------------------
Would... (6 Replies)
Discussion started by: soliberus
6 Replies
4. Solaris
We need a DNS Server on DNS 10. What the best product can i buy and install ?
Help me, pls.
Tks all. (1 Reply)
Discussion started by: quan0509
1 Replies
5. Solaris
Hello
We have recently been through an audit of our solaris servers.
All our solaris servers are running version 10.
We have been told to close down all the services and we have closed what we could by using svcadm disable
We only wish to let ssh and the ftp service to run.
Below is a... (3 Replies)
Discussion started by: sollyshah
3 Replies
6. Solaris
I need to know how to Manage Solaris services (SMF) in sparse zone with Solaris container manager.
I have navigated all the documentation and I have not found any clue.
I installed the Sun management center (SMC) server on a server box and the agents on others. I can manage the SMF of the global... (5 Replies)
Discussion started by: ibroxy
5 Replies
7. Solaris
I normally use "chkconfig" to configure start up services in a particular run level.....
But i don't know how to do it in solaris 10.... please help me !!! (2 Replies)
Discussion started by: vamshigvk475
2 Replies
8. Solaris
Hi,
Few services not starting on new build Solaris 11 non-global zone. I uninstalled zone and reinstalled and still same issue, while global zone is working fine.
smpt service is going into maintenance mode and /var/svc/log/network-smtp:sendmail.log shows that it tries and then dead
... (0 Replies)
Discussion started by: solaris_1977
0 Replies
LEARN ABOUT MOJAVE
stopped
stopped(7) Miscellaneous Information Manual stopped(7)
NAME
stopped - event signalling that a job has stopped
SYNOPSIS
stopped JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
DESCRIPTION
The stopped event is generated by the Upstart init(8) daemon when an instance of a job has stopped. The JOB environment variable contains
the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs.
If the job was stopped normally, the RESULT environment variable will be ok, otherwise if the job was stopped because it has failed it will
be failed.
When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start,
main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job was stopped because it hit the respawn
limit.
Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either
EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received.
The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see
init(5) for more information.
If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not
found). See the system logs for the error.
init(8) emits this event as an informational signal, services and tasks started or stopped by this event will do so in parallel with other
activity. It is typically combined with the starting(7) event by services when inserting themselves as a dependency.
Job configuration files may use the export stanza to export environment variables from their own environment into the stopped event. See
init(5) for more details.
EXAMPLE
A service that wishes to be running whenever another service would be running, started before and stopped after it, might use:
start on starting apache
stop on stopped apache
A task that must be run after another task or service has been stopped might use:
start on stopped postgresql
SEE ALSO
starting(7) started(7) stopping(7) init(5)
Upstart 2009-07-09 stopped(7)