From: A. Mahendra Rajah (Mahendra.Rajah@URegina.CA)
Date: Thu Jun 16 2005 - 18:05:20 EDT
We are running Tru64 v5.1B-3 (= v5.1B-2 + pkit#5) on an ES40.
Before pkit#5 was applied, we had an application 'prtcontrol'
added to the DOP database that worked fine for authorized
usernames before _and_ _after_ pkit#5.
I made some modifications to the ksh script used by
'prtcontrol' and noticed that DOP was still using the original
version of it. Question #1: Why was it still looking at the
original version? It no longer exists in its original directory!
OK, so I thought I would do a 'dop -d', 'dop -a' and 'dop -W'
to get it reinstalled in the dop database.
But now, for the 'root' user 'dop prtcontrol' works using the
modified ksh script. For the usernames that have been already
authorized to run 'prtcontrol', the dop command returns this
error:
A system error occurred, preventing prtcontrol from
being launched. The application you wish to access is
not available on this system. It may be contained in a
subset that is not currently installed.
Funny thing is that the same error is returned if this user
tries 'dop somegarbage' where 'somegarbage' is not even in the
dop database.
So, I thought that there may be an access violation problem?
/etc/doprc.bin had '-rw-------' for protection and I modified
that to '-rw-r--r--', but the error message persists!
Any insight into what is going on here and how can I convince
'dop' to do its job for my users?
Thanks in advance,
-- mahendra
.................................................................
A. Mahendra Rajah Email: Mahendra.Rajah@URegina.CA
Tru64 UNIX Systems Manager Phone: (306) 585-4496
Dept. of Computing Services FAX: (306) 337-2324
University of Regina,
Regina, Sask., S4S 0A2
Canada.
.................................................................
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:19 EDT