11-20-2014
Thanks Bakunin for your reply.
We were using a performance monitoring tool, my query is what are the parameters (Services or Process) need to configure on monitoring to capture the instance like shutdown, restart or halt status of SAP & DB2.
Hope I clarified in depth.
8 More Discussions You Might Find Interesting
1. HP-UX
We just recently moved from a DG-UX (Unix V) to HP 9000 servers running POSIX. I used the c-shell in the DG-UX system mainly because the bourne-shell did not support aliasing. Now in the default posix-shell of HP aliasing is supported. The main difference seams to be that in a c-shell you can pass... (1 Reply)
Discussion started by: vslewis
1 Replies
2. AIX
Hi everyone.
I am currently looking for a monitor to monitor my DB2 UDB database, which runs on AIX 5.3. Does anyone here use any good ones or has anyone heard of any good ones?
I especially need to monitor which applications run at any given time, so that I am able to ballance the workload... (0 Replies)
Discussion started by: sprellari
0 Replies
3. Shell Programming and Scripting
I have a db2 stored procedure on my database which require 3 parameters, I have the following db2 command in a sql script
CONNECT TO SAMPLE;
CALL BACKUP(INPUT_1, INPUT_2, INPUT3);
Usually, I would just invoke this sql script from my shell script like below
db2 -tf... (1 Reply)
Discussion started by: mpang_
1 Replies
4. Shell Programming and Scripting
hi all,
i would like to write the shell script to monitoring the processing, but if i passing the parameter the number of process is incorrect
how to slove it? many thx
got the correct number of process as following script:
===========================================================... (3 Replies)
Discussion started by: eric_wong_ch
3 Replies
5. AIX
Hello,
I was wondering if I have 3 nodes (A, B, C) all configured to startup with HACMP, but I would like to configure HACMP in such a way:
1) Node B should startup first. After the cluster successfully starts up and mounts all the filesystems, then
2) Node A, and Node C should startup !
... (4 Replies)
Discussion started by: filosophizer
4 Replies
6. UNIX for Dummies Questions & Answers
AIX & DB2 paging issues
Hello I needs some help on AIX & DB2 paging issues. Recently a db2 query caused paging issues which then lead to memory problems and a server restart. Is there anyway of finding out what db2 queries were causing the problem..
Thanks in advance (2 Replies)
Discussion started by: nedkao
2 Replies
7. Shell Programming and Scripting
GM everyone,
I have this script that goes to multiple servers and monitor a certain process and send the output to a file on servers1, the script looks like this
exec < server.list
while read SERVER
do
ssh $SERVER "ps -ef | grep process_name" >> /tmp/report
done
can someone help ad... (0 Replies)
Discussion started by: baders
0 Replies
8. Shell Programming and Scripting
I am writing a script to kick off a process to gather logs on multiple nodes in parallel using "&". These processes create individual log files. Which I would like to filter and convert in CSV format after they are complete. I am facing following issues:
1. Monitor all Processes parallelly.... (5 Replies)
Discussion started by: shunya
5 Replies
LEARN ABOUT POSIX
systemd-halt.service
SYSTEMD-HALT.SERVICE(8) systemd-halt.service SYSTEMD-HALT.SERVICE(8)
NAME
systemd-halt.service, systemd-poweroff.service, systemd-reboot.service, systemd-kexec.service, systemd-shutdown - System shutdown logic
SYNOPSIS
systemd-halt.service
systemd-poweroff.service
systemd-reboot.service
systemd-kexec.service
/lib/systemd/systemd-shutdown
/lib/systemd/system-shutdown/
DESCRIPTION
systemd-halt.service is a system service that is pulled in by halt.target and is responsible for the actual system halt. Similarly,
systemd-poweroff.service is pulled in by poweroff.target, systemd-reboot.service by reboot.target and systemd-kexec.service by kexec.target
to execute the respective actions.
When these services are run, they ensure that PID 1 is replaced by the /lib/systemd/systemd-shutdown tool which is then responsible for the
actual shutdown. Before shutting down, this binary will try to unmount all remaining file systems, disable all remaining swap devices,
detach all remaining storage devices and kill all remaining processes.
It is necessary to have this code in a separate binary because otherwise rebooting after an upgrade might be broken -- the running PID 1
could still depend on libraries which are not available any more, thus keeping the file system busy, which then cannot be re-mounted
read-only.
Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in
/lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen
action. All executables in this directory are executed in parallel, and execution of the action is not continued before all executables
finished.
Note that systemd-halt.service (and the related units) should never be executed directly. Instead, trigger system shutdown with a command
such as "systemctl halt" or suchlike.
SEE ALSO
systemd(1), systemctl(1), systemd.special(7), reboot(2), systemd-suspend.service(8)
systemd 237 SYSTEMD-HALT.SERVICE(8)