Home » forums » Luminis Platform / System

privs for luminis admin to start/stop cp

Submitted by Tom on Wed, 2010-09-01 11:47

We're trying to get from redhat 3 to redhat 4 for Luminis IV. The sys admin who set up our current systems is gone. Working with the new sys admin, I'm trying to replicate the functionality of our RH 3 system on RH 4.

The sticking point is that from the luminis admin OS account, I can't issue startcp or stopcp, it is demanding the root password.

The sudo-ers setup has been replicated. It looks good ... at least it's the same on the new RH 4 host as it is on the production RH 3 host. Far as I can tell, I have /etc/passwd and /etc/group right.

Is there something new I need to do for RH 4?

‹ replicator: different admin.id for target system? Discuss major functional differences between Luminis 4.x.x releases ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

I found it, sort of. I need

Submitted by Tom on Wed, 2010-09-01 13:21.

I found it, sort of. I need a value for SUDO set. I see it is set on the production host but I can't tell where. Suggestions?

Sungard sent info for Solaris for Luminis III saying to set it in the admin account's .profile. I did

export SUDO=`which sudo`

since it's in the path. That works but may not be the best way. Suggestions?

rc-common

Submitted by ToddTrann on Wed, 2010-09-01 13:25.

Check rc-common in /opt/pipeline/bin/rc/

But hey if setting it in .profile works, you can run with that, and not have to patch rc-common after every upgrade

found it

Submitted by Tom on Wed, 2010-09-01 13:33.

The previous admin had added it to .cprc.

So ... I'm good to go.

Syndicate content