It depends on the signal you use. A standalone "kill" or a "kill -15"
yes. That's called SIGTERM, all it does is send a termination signal to
the process.
https://major.io/2010/03/18/sigterm-vs-sigkill/
-
Thanks,
Marc...
Marc Lanteigne
Spe
So you are saying that issuing the server HALT command via console is no
different than the OS level kill?
On Tue, Mar 12, 2019 at 9:15 AM Marc Lanteigne
wrote:
> That's what I said.
>
> > From the /etc/init.d/tsminst1 wrapper script, it does do a kill
> > command, but without any signal, which
That's what I said.
> From the /etc/init.d/tsminst1 wrapper script, it does do a kill
> command, but without any signal, which means it defaults to -15
> (SIGTERM). That sends a message to the process to shutdown gracefully.
It's in the manual as one of the proper ways to start/stop the server:
tsminst1 is a script in /etc/rc.d/init.d which determines the pid of the
running dsmserv process and then issues a kill against it. From the
tsminst1 script
stop() {
echo "Stopping $prog instance $instance ..."
if [[ -e $pidfile ]]
then
# make sure someone els
"systemctl stop tsminst1" is not a kill. That's a service command to tell
the application it manages to shut down gracefully.
>From the KC:
https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.0/srv.install/t_srv_startsrv_autolnx-linux.html
6.To start or stop the server, issue one of the
regards,
Eric van Loon
Air France/KLM Storage & Backup
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of J.
Eric Wonderley
Sent: maandag 11 maart 2019 17:36
To: ADSM-L@VM.MARIST.EDU
Subject: Re: best way to avoid long rollback
We are running rhel7
Out of curiosity, why do you do a "systemctl stop tsminst1" (which if I
recall does a kill) vs just HALT the ISP server immediately after the DB
backup finishes? Our patching takes about the same time (we do it monthly)
since the IBM lin_tape drivers have to be removed before kernel patching
and t
We are running rhel7 on a dell r730 and we just did a full and
dbsnap...ususally take about 1.5h for both to complete.
Typically then shutdown with systemctl stop tsminst1.
I think last time we stopped tsm about an hour after the db finished its
backups. Likely restarted tsm about an hour after
I have to ask what OS/hardware/ISP are you running? What procedure are you
using to prep for the OS patching (we stop client sessions/all admin
processes - do a full DB backup - halt the server)
Our offsite replica server is RHEL 7 on Dell R740xd with 192GB and 3TB SSD
with the DB currently at 2
