Ok,

Disclaimer #1 - I have never tried this.
Disclaimer #2 - I'm not painfully familair with solaris ( that's my guess at the os 
you're using )

BUT.. in theory ( cracks knuckles ), if your user account(s) had rw access to the 
Drives/Library ( i.e. /dev/XXXX ), the TSM process ( i.e. daemon ) _should_ be allowed 
to run in user space, given that any port >1024 is unprivileged.  

I don't know what sort of dependancies the drivers might hold on needing root 
privileges, but even if the SysAdmin made a disk group and changed the devices to be 
owned and rw by that group, I don't see why it couldn't be done.

well, there's my 2cents.  change is expected.

-ed


Ed Anderson
Unix Systems Administrator
University of Mississippi Medical Center
[EMAIL PROTECTED]

>>> [EMAIL PROTECTED] 2002/02/08 03:16:11 PM >>>
Our company uses Powerbroker access instead of sudo and they don't want to
give us
pbrun su-root privileges. Any other ideas?

-----Original Message-----
From: PINNI, BALANAND (SBCSI) [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 11:47 AM
To: [EMAIL PROTECTED]
Subject: Re: root required to kill TSM daemons?


Pl look at sudo command acts as proxy for root only for that cmd.
BALANAND

-----Original Message-----
From: Cheryl Miller [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 08, 2002 12:41 PM
To: [EMAIL PROTECTED]
Subject: root required to kill TSM daemons?


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
getting hung schedulers and need to be bounced to resume working. The fact
that root privileges are needed to bounce the daemons is adding on days to
our resolution, since we have to open a problem ticket with the system
admin. group and wait for them to bounce the daemons. We have ids on most of
the unix servers and could do it, if the permissions allowed.

Any ideas?? Do any of you have a work around for this problem? Tivoli had me
open an enhancement request.

....Cheryl

Cheryl Miller
Wells Fargo Bank
Distributed Storage Management (DSM)
916-774-2073

Reply via email to