sudo instead of root on TS 5.5.2

Hi,

On pages 30 and 48 of the TS5.5.2 admin guide for Solaris (I'm running 2.8), Interwoven recommends against logging in as root with sudo and alludes to "very bad things" happening if you do.

I was curious if anyone has encountered problems using sudo after the install.

For example, will I totally jack my installation if I use sudo to iwreset or /etc/init.d/iw.server stop??

What about using sudo to iwadduser.ipl ?? Any issues.

It'd be great to hear of any warnings from Interwoven. I know Bob Walden is out there somewhere, being helpful to someone. Share the love, Bob. Share the love.

Tom

Find more posts tagged with

Comments

Migrateduser

??? How did I become so notorious??? :-)

You can use su ( *not* sudo) to your heart's content to become root to perform root-only (appendix G) operations after installation. None of the examples you give should be problematic.

I'm not familiar with sudo, so I can't comment on it specifically, but I'll ask a question instead: why would you use it instead of su -? (And for all those out there playing the home version of our game, don't forget the dash with the su command when assuming root. The dash makes the session a login shell, with correct PATH, HOME, etc.

bw

Bob Walden [bob.walden@interwoven.com]
Interwoven Education Group
IM: Yahoo, MSN bob_walden

tvaughan

As one's level of helpfulness on a board increases, so goes one's level of notoriety ;-)

Sudo is just some program that lets the root user assign other, non-users the right to execute commands as if they were root.

The reason I would use this is because my Unix System Administration department is so protective of their right on their machines that they won't let me in their little root club, even if it means the end result is a terrible level of support to the end-users of TeamSite (they ask me, the TS Admin to do something, and then I have to wait for 1-5 days for the sysadmins to get around to doing it).

They've set me up with a pretty extensive sudo-priveledge list for day-to-day chmods and chowns, etc. But if something unexpected arises, I'm at their mercy.

To all those would be TeamSite admins out there following at home:

avoid getting yourself into this scenario at all costs.

It blows.

Tom