02-13-2017
Quote:
Originally Posted by
RavinderSingh13
Hello Lord Spectre,
Definitely it will be useful for people, could you please add that which configuration file you have made the changes so that a non-unix admin person(eg--> me) could also understand it more clearly. Will be grateful to you.
Thanks,
R. Singh
Yes sure, first post edited with related info.
Last edited by Lord Spectre; 02-13-2017 at 02:12 PM..
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I just installed red hat 7.2 on my laptop. it's dual booted with xp and red hat. when i boot in to linux it boots up to the screen to ask me my name and pass....i put in root and my password. after this it goes to a blue screen and sits there. the after about 2 minutes it comes up with a fatal... (1 Reply)
Discussion started by: muzscman
1 Replies
2. AIX
As topic, assume we have a service called "blahservice"
and we can start it by:
startsrc -s blahservice
what is the best practice to run such command when system start?
- directly use mkitab to add it into /etc/inittab
or
- drop startup scripts in /etc/rc.d/rcX.d
I know they... (4 Replies)
Discussion started by: acerlinux
4 Replies
3. Red Hat
Hello,
How do I see what IP addresses are connected to my machine?
thanks (2 Replies)
Discussion started by: sonomao
2 Replies
4. Red Hat
hi,
i am using RHEL 5 and i am not able to on the vsftp
i have tried to on the vsftp service using command
service vsftpd start
Starting vsftpd for vsftpd:
i am posting the content of my /etc/xinetd.d/vsftpd file
# description: The vsftpd FTP... (2 Replies)
Discussion started by: u.n.i.x
2 Replies
5. Red Hat
Today I have installed VSFTPD but service is failing to start.
We have been using standard FTP successful but need to introduce an FTPS option.
I have run YUM install VSFTPD and everything appeared to load ok.
(If I run rpm - qa | grep vsftpd I get vsftpd-2.0.5-16.el5_4.1 which I... (4 Replies)
Discussion started by: PaulComins
4 Replies
6. Red Hat
Hi There,
I have been googling for this error and try solution provided but still not avail to resolve Kickstart Issue.
Any expert have encounter this problem? Thanks.
Regards,
Regmaster (4 Replies)
Discussion started by: regmaster
4 Replies
7. UNIX for Dummies Questions & Answers
how to know if i use "Red Hat Enterprise Linux" or "Red Hat Desktop" ? (2 Replies)
Discussion started by: ahmedamer12
2 Replies
8. Red Hat
Hello everyone,
I'm setting up a cluster with 2 nodes using Red Hat enterprise 6.2 x86_64, 1 luci and 1 ricci for education purpose.
Ricci is installed and already running and luci is installed and running but at the time of add and create the cluster through the web gui it give me a error... (1 Reply)
Discussion started by: typeav
1 Replies
9. Red Hat
Hi there,
I am wondering if I could add start/stop ksh scripts provided by 3rd party to cluster... I read that script must be ocf/lsb compliant, however, in AIX I can just set up two separate scripts for starting and stopping application. Can similar be done under RH Linux cluster?
Cheers,
c (1 Reply)
Discussion started by: cyjan
1 Replies
LEARN ABOUT LINUX
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)