03-27-2015
Prioritizing scripts under /etc/init.d/
Hello Team,
I work on IBM TWS ( Tivoli Workload Scheduler ) administration. I have placed TWS service stop and start script under directory /etc/init.d/ in my Linux server and coded email alert when the script has been executed with stop or start parameter .
I am receiving email notification only when start parameter has been passed to script after server reboot.
But I also expect email notification when server gets shutdown. Meaning when stop parameter passed to the script I am not receiving the email.
After analyzing the situation I found sendmail service is getting stopped before TWS service stop script executed.
Is there any way I could prioritize the execution of TWS service stop script before send mail function killed/stopped during the server shutdown.
And start the sendmail before start parameter passed to the TWS service script.
Kindly assist.
Regards,
Madhusudan
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Where are they located? (2 Replies)
Discussion started by: 98_1LE
2 Replies
2. UNIX for Advanced & Expert Users
Hi Expert,
I have encountered some problem with my SUN system. Everytime when i issue command #init 6 OR #init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init 0..
I can only reboot the system using reboot ... Was... (6 Replies)
Discussion started by: sc2005
6 Replies
3. Linux
Dear all,
I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel):
1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins
So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies
4. Red Hat
In the olden days it used to be /etc/inittab.
Then it got changed to /etc/event.d/tty* under Fedora 10.
Can someone please point out what it is now in Fedora 13? I want to run mgetty which I had configured in Fedora 10 as /etc/event.d/ppp0:
# modem - getty
#
# This service maintains a... (1 Reply)
Discussion started by: druidmatrix
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
I am experiencing a weird thing on my SUNFIRE machine with Solaris 9 OS.
When I do init 0 to shutdown the machine to go to ok prompt, what it did was shutdown and reboot like an init 6 command do. I did check the corresponding rc scripts that were involved with init 0 and compared with rc... (2 Replies)
Discussion started by: Yenthanh
2 Replies
6. Solaris
i did my research in finding the answer but couldn't find right one. Please give your inputs. (6 Replies)
Discussion started by: ranumala
6 Replies
7. Red Hat
I encountered a problem on one of our database servers.
OS: CentOS 5.5 final
Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel)
We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies
8. UNIX for Advanced & Expert Users
Why not just init? What do /etc/rc*.* scripts, rc*.*d and init*.*d directories and directory trees, etc (ex like svc, startsrc, and on and on) do that init and inittab do not or could not do? Is it just so novice SysAdmins need not mess with init?
Is there an overview anyplace of how start-up... (4 Replies)
Discussion started by: Clovis_Sangrail
4 Replies
9. UNIX for Dummies Questions & Answers
One of our VM machines mysteriously went read-only overnight and as it wasn't being used, thought it would be a good idea to reboot the machine and run fsck on boot, well. . . .. things didn't quite work out that way lol :)
Anyway, the machine booted up, but mysteriously had no hostname set,... (2 Replies)
Discussion started by: jimbob01
2 Replies
LEARN ABOUT OPENDARWIN
service
SERVICE(8) System Manager's Manual SERVICE(8)
NAME
service - run a System V init script
SYNOPSIS
service SCRIPT COMMAND [OPTIONS]
service --status-all
service --help | -h | --version
DESCRIPTION
service runs a System V init script or systemd unit in as predictable an environment as possible, removing most environment variables and
with the current working directory set to /.
The SCRIPT parameter specifies a System V init script, located in /etc/init.d/SCRIPT, or the name of a systemd unit. The existence of a
systemd unit of the same name as a script in /etc/init.d will cause the unit to take precedence over the init.d script. The supported val-
ues of COMMAND depend on the invoked script. service passes COMMAND and OPTIONS to the init script unmodified. For systemd units, start,
stop, status, and reload are passed through to their systemctl/initctl equivalents.
All scripts should support at least the start and stop commands. As a special case, if COMMAND is --full-restart, the script is run twice,
first with the stop command, then with the start command.
service --status-all runs all init scripts, in alphabetical order, with the status command. The status is [ + ] for running services, [ - ]
for stopped services and [ ? ] for services without a status command. This option only calls status for sysvinit jobs.
EXIT CODES
service calls the init script and returns the status returned by it.
FILES
/etc/init.d
The directory containing System V init scripts.
/{lib,run,etc}/systemd/system
The directories containing systemd units.
ENVIRONMENT
LANG, LANGUAGE, LC_CTYPE, LC_NUMERIC, LC_TIME, LC_COLLATE, LC_MONETARY, LC_MESSAGES, LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEA-
SUREMENT, LC_IDENTIFICATION, LC_ALL, TERM, PATH
The only environment variables passed to the init scripts.
SEE ALSO
/etc/init.d/skeleton
update-rc.d(8)
init(8)
invoke-rc.d(8)
systemctl(1)
AUTHOR
Miloslav Trmac <mitr@redhat.com>, Petter Reinholdtsen <pere@hungry.com>
Licence: GNU Public Licence v2 (GPLv2)
COPYRIGHT
2006 Red Hat, Inc., Petter Reinholdtsen <pere@hungry.com>
Jan 206 SERVICE(8)