Sponsored Content
Top Forums UNIX for Advanced & Expert Users rc scripts, do i need to kill them on shutdown? Post 34229 by RTM on Monday 10th of February 2003 09:57:27 AM
Old 02-10-2003
It would matter on what the script was starting/killing. You can go from multi user mode to single user without shutting down the server and coming back up to single user. I don't know many folks that do this - I believe it used to be to get clean dumps of filesystems. But the point is, if you did do it, then you would not want certain services/processes/daemons running that would allow folks access into your server while you were doing something that required a "quiet" system.

If you look at some of the "kill" scripts, you might notice that they are just looking via the ps command for a certain process and killing it or checking a xxxx.pid file for the pid that was last started for a certain service and killing that pid.

It is a matter of personal choice - if you ever had to clean up /tmp after folks failed to clean up after themselves, then you should program as if you were the one who has to clean up after everyone else. You remove your temp files and put kill scripts for your processes. Just my 2 cents worth.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Shutdown Scripts

Hi, Recently I've created a script to shutdown a few hpux workstations and I found out that the script can only shutdown 1 workstation and then exit out from the loop without shutting down the rest of the workstation. The scripts is as below (brief one): hcp_list="machine_a ... (4 Replies)
Discussion started by: zheng_soon
4 Replies

2. SuSE

Shutdown scripts

Hello all I'm trying to automate the startup/shutdown of my database whenever the OS is bounced ... OS : Linux (Kernel : 2.4.20.-6) Oracle : 9.2.0.5 The contents of /etc/init.d/dbora file is listed below case "$1" in 'start') su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/dbstart"... (1 Reply)
Discussion started by: luft
1 Replies

3. AIX

Startup/Shutdown scripts

I understand that by putting in entries into the /etc/inittab file. We can actually call the our scripts during startup. mkitab "start_server:2:once:sh /scripts/startserver.sh" Would the system wait for startserver.sh finish executing before it goes to another entry? and how long would it... (1 Reply)
Discussion started by: vincente
1 Replies

4. UNIX for Advanced & Expert Users

connection to localhost:10.0 host broken (explicit kill or server shutdown)

Hi All, We use tomcat web server and it will get terminated with below error: connection to localhost:10.0 host broken (explicit kill or server shutdown) Please let me know how to fix this error. (5 Replies)
Discussion started by: bache_gowda
5 Replies

5. UNIX for Dummies Questions & Answers

Startup/Kill Scripts

Hello, I have to perform an audit of a system at work and I am looking at its /etc/rc3.d: K01tog-pegasus K74nscd S08iptables S50openemm K01yum K74ntpd S09isdn S55cups K02NetworkManager K85mdmpd S09pcmcia S55sshd K03rhnsd ... (8 Replies)
Discussion started by: mojoman
8 Replies

6. AIX

Startup/shutdown scripts in AIX

hi, If we place Sxx (startup script) and Kxx(shutdown script) in /etc/rc.d/rc2.d,then it would start and stop automatically(assume they are linked to other script that actually starts/stops). is there really a link needed here to /etc/rc.d/init.d? if not,what is the use of this directory..?... (1 Reply)
Discussion started by: to_bsr
1 Replies

7. AIX

Please update inittab/rc.shutdown/rc scripts to start/stop mqm (need help Urgent)

HI i need help from seniors on this issue, i need to know how to do this, i need to update 50+ server starting saturday. below is the ticket which i have with full description. Currently MQ Series must be stopped before and started after any reboot. Not having the start/stop as part of... (2 Replies)
Discussion started by: gulamibrahim
2 Replies

8. Shell Programming and Scripting

Oracle DB Start shutdown scripts

Hi, We have a requirement wherein we do not want to share the Oracle DB sys and system passwords to be shared with the support desk. But they will be responsible for starting/shuting down the Database. Is it possible to write a shell script which will read the sys and system passwords from a... (0 Replies)
Discussion started by: narayanv
0 Replies

9. AIX

X connection to localhost:10.0 broken (explicit kill or server shutdown)

I want to run applet on AIX 6 machine. I already have setup $DISPLAY variable for putty session by selecting X11 option. I got below error for any X related commands (xclock, X, applet viewer ) X connection to localhost:10.0 broken (explicit kill or server shutdown). Please can anyone... (0 Replies)
Discussion started by: kailas.girase
0 Replies

10. Red Hat

Boot/Shutdown scripts

Server: Redhat 6.2 Goal: Startup script/Shutdown Script Overview: I'm just doing a very basic test. I'm not getting chkconfig involved. Research so far: I've found a few different ways of getting this to work, some say I can just drop the scripts in the corresponding rc directory. Others... (4 Replies)
Discussion started by: HayekSplosives1
4 Replies
KILL(2) 						      BSD System Calls Manual							   KILL(2)

NAME
kill -- send signal to a process SYNOPSIS
#include <signal.h> int kill(pid_t pid, int sig); DESCRIPTION
The kill() function sends the signal given by sig to pid, a process or a group of processes. Sig may be one of the signals specified in sigaction(2) or it may be 0, in which case error checking is performed but no signal is actually sent. This can be used to check the valid- ity of pid. For a process to have permission to send a signal to a process designated by pid, the real or effective user ID of the receiving process must match that of the sending process or the user must have appropriate privileges (such as given by a set-user-ID program or the user is the super-user). A single exception is the signal SIGCONT, which may always be sent to any descendant of the current process. If pid is greater than zero: Sig is sent to the process whose ID is equal to pid. If pid is zero: Sig is sent to all processes whose group ID is equal to the process group ID of the sender, and for which the process has permission; this is a variant of killpg(2). If pid is -1: If the user has super-user privileges, the signal is sent to all processes excluding system processes and the process sending the signal. If the user is not the super user, the signal is sent to all processes with the same uid as the user excluding the process sending the signal. No error is returned if any process could be signaled. For compatibility with System V, if the process number is negative but not -1, the signal is sent to all processes whose process group ID is equal to the absolute value of the process number. This is a variant of killpg(2). RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error. ERRORS
Kill() will fail and no signal will be sent if: [EINVAL] Sig is not a valid signal number. [ESRCH] No process can be found corresponding to that specified by pid. [ESRCH] The process id was given as 0 but the sending process does not have a process group. [EPERM] The sending process is not the super-user and its effective user id does not match the effective user-id of the receiving process. When signaling a process group, this error is returned if any members of the group could not be signaled. SEE ALSO
getpid(2), getpgrp(2), killpg(2), sigaction(2) STANDARDS
The kill() function is expected to conform to IEEE Std 1003.1-1988 (``POSIX.1''). 4th Berkeley Distribution April 19, 1994 4th Berkeley Distribution
All times are GMT -4. The time now is 08:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy