Len, you bring up a good point.

NetBackup has a script called bpkillall or something like that.  It did a ps
-ef | grep bp looking for what was necessary to kill and issued a kill -9
against each one of the tasks.  Why could they just not create a script with
the sticky bit on it that executes as root that kills each of the tasks.

Our folks always had to log on as root to do NetBackup administration
because like TSM it was installed with root only permissions.  Not saying
that is the right way to do it, but it was the way it was done.

-----Original Message-----
From: Len Boyle [mailto:[EMAIL PROTECTED]]
Sent: Sunday, February 10, 2002 11:28 AM
To: [EMAIL PROTECTED]
Subject: Re: root required to kill TSM daemons?


In article <[EMAIL PROTECTED]>, Cheryl Miller
<[EMAIL PROTECTED]> says:
>
>We just converted to TSM 4.2.1.9 from NetBackup. We are finding that
>our group needs to be able to stop the TSM daemons and start the start
>up script, instead of always having the system admin. do this. Right
>now I am told that there is no work around for root privileges being
>needed to kill the TSM daemons. I'm wondering how other shops get
>around this problem? When our TSM server crashes, all of the clients
>that are getting backed up are Any ideas?? Do any of you have a work
>around for this problem? Tivoli had me open an enhancement request.
>
>....Cheryl

Hello Cheryl

How did you handle this with NetBackup. As that normally runs using root?

Maybe we can attack this from the other side. Tell us a little more about
your tsm software level. The type of hardware, the os and os level for the
tsm server and clients. What are the error messages that come out just
before the tsm server process dies.

For the most part you should not be seeing crashes and hangs. Maybe if you
can tell us a little more about your setup and the errors we can help point
you to a more stable  environment.

Regards len


-------------------------------------------------------------------------
Leonard Boyle                               [EMAIL PROTECTED]
SAS Institute Inc.                          ussas4hs@ibmmail
Room RB448                                  [EMAIL PROTECTED]
1 SAS Campus Drive                          (919) 531-6241
Cary NC 27513

Reply via email to