Assume: $/usr/sbin/rcmgr get SECURITY BASE
BASE
Upstairs, I run eXcursion's version V3.0.571 of the Common Desktop
Environment on a Windows95 platform. I like it very much but the
login_shell for this CDE does not allow for root logins.
Downstairs, the CDE login_shell running on our Digital Unix Alpha
server does allows for root logins.
I run a lot of SysAdmin type programs and prefer to run these programs
upstairs. Some of these applications are smart enough to querry
whether they should run as root or whether they should just run under
my username by throwing up a root nag screen. However many of the
SysAdmin type applications that I use are not nag-enabled and have to
be GUI-ed up the old fashion way by executing them via name from a
terminal window after su-ing to root. Since my memory isn't that
good, I have to hunt down the name of these application before they
can be executed. This a hassle. I just want to click on an icon.
For example, when you click on the NetWorker 5.2 icon there is no root
nag screen. However should it find my USERNAME on its built in list
of administrators, it will allow me to administer the product. In
order to get my name on that list though, I had to su to root and GUI
up the old fashion way, after that adding myself was easy. Hehehe,
hopefully that is the only time we have to do that. We are just now
enable-ing the product and we don't have a feel for it yet.
So to make a long story short, I am not getting enough nags, but the
nags I do get, I would rather not see. If I could just sign in as
root upstairs I could eliminate this problem. Who is placing this
restriction on me? Is it UNIX, the CDE, or something built into
eXcursion? I have access but its hard to use; know what I mean?
Does anyone have a configurement fix for this problem?
General points of information for or against are appreciated.
- Thanks Kevin
Received on Mon Nov 16 1998 - 21:15:30 NZDT