--DIOMP1UsTsWJauNi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 11, 2003, [EMAIL PROTECTED] wrote:
> Does openpkg's rc script depend on /usr/ucb/whoami ? Is there a better wa=
y to
> check simply that a user has effective id root? I'd like to avoid having =
to add
> /usr/ucb to root's PATH if possible, and more importantly avoid probs wit=
h 'su'
> vs. 'su -', etc.
>
[...]
>
> # who am i
> guest      pts/4        Feb  9 19:37    (laptop-a)
> # whoami
> root
> #=20

Hello Vinod,

Yes, this is a known problem. Today's OpenPKG 'rc' bourne shell bundled with
OpenPKG 1.[0-2] prefers 'whoami' to discover the username, but will use 'wh=
o'
as the next alternative. It seems that you've learned this yourself the hard
way, because running 'who am i' does not return the correct username in some
cases.

I expect that a fully rewritten 'rc' program will be bundled with OpenPKG 2=
.0,
and the bug you reported will then be solved. Until then, the work around is
to truly log in as root or have the 'whoami' command appear before 'who'
according to the PATH variable of your environment.

--
[EMAIL PROTECTED]
Development Team, Application Services
Cable & Wireless Deutschland GmbH

--DIOMP1UsTsWJauNi
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia+4K

iQEVAgUBPkt6tVuYv80UoVTdAQHh/Qf9ESBBsxdWAeUNKf6fTfalI3XEpM6Tam7s
Kj9dRW0AJAttl/nANFS7hg5hV1jHuZVGxAUjqQDsgEqk+wl9sMX0z8ieDi9PRVRU
N9GuDJyQBeK/yKnah+SKrxPB854Ki5H8bVw2jLXq+PDMLfGLievdnckGZbCoqti/
FRtv74j7++eJRNOlAxDhKdZTJr338+pMkP5ZSTFRd9udhKxrf7/fj3hc/M0TjwVv
Akyv0NboQKSkJxdR4NIBMkvuCvF9kSAkrex2w/wzO29U5CEtNqhw4fZH326xpv30
bkOidOSW9YtzPQJ2iQYhbHhxfi4Rgq9owoKE8dnvRJcdPxKSVsimAA==
=QFgB
-----END PGP SIGNATURE-----

--DIOMP1UsTsWJauNi--
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   [EMAIL PROTECTED]

Reply via email to