Re: user permission problems
- From: "Brian K. White" <brian@xxxxxxxxx>
- Date: Fri, 4 Apr 2008 23:23:59 -0400
----- Original Message -----
From: "Nico Kadel-Garcia" <nkadel@xxxxxxxxx>
Newsgroups: comp.unix.sco.misc
To: <andrewm659@xxxxxxxxx>
Sent: Friday, April 04, 2008 6:31 PM
Subject: Re: user permission problems
andrewm659@xxxxxxxxx wrote:
Its not there. I can't find it on skunkware either. Can you help me
out? Do you have it for SCO Openserver 5.0.6?
On Mar 27, 9:08 pm, Nico Kadel-Garcia <nka...@xxxxxxxxx> wrote:
On 27 Mar, 13:44, "andrewm...@xxxxxxxxx" <andrewm...@xxxxxxxxx> wrote:
I seem to be having some trouble with OpenServer 5.0.6. I need to beInstall sudo. It's much more flexible and ocnfigurable than the
able to give permission to other users to do various tasks on the
system, such as kill users and add and remove users and printers. I
set them up in the tcb and copied the kill command to their home dir.
When they go to hit 'w' for the who command, it only shows them as
logged in. I'm not sure why. Could you please help?
"asroot" utility, it's used throughout the UNIX and Linux communities,
it's well documented, and Brian White's site atftp://pcunix.com/has
both patched source and binaries.
Please read the last line of my post, where it said:
Brian White's site atftp://pcunix.com/has both patched source and binaries.
He may not have deduced where on pcunix.com to look.
My directory there is /pub/bkw
The binary and manpages tar for sudo is here:
ftp://pcunix.com/pub/bkw/sudo.tar.bz2
You will need to install oss646c first.
If you don't have bzip2 to unpack the tar.bz2, and can't install gwxlibs, then there is a binary here:
ftp://pcunix.com/pub/bkw/bzip2.tar.Z
However, I don't beleive you need sudo anyways.
asroot is already there and does work fine.
Only if you actually needs some feature asroot can't handle would I bother with sudo.
As for why users who run w can't see other users?
You said you set up the kill command successfully, but then complained that the w command doesn't work.
If you need them to be able to run w with root privs, then you have to set up the w command the same way.
When I run w as a user I see everything, but, w (and who, and finger) gets much of it's info from /etc/utmp
/etc/utmp is just a file that various programs update when users login,logout, or issue commands.
It can become out of sync with reality or corrupt to a small or large degree lots of different ways.
So, any time any of the utmp/wtmp/utmpx/wtmpx reading commands acts at all funny, one easy step to try is to reset those files. The only difficulty is ideally you should reboot or at least switch to single-user mode to do it and then immediately reboot afterwards back to normal mode.
cd /etc
utmpshutdown -g0 -i6 y
utmpx
wtmp
wtmpx
Another possible hint comes right from "man w"
---snip---
Authorization
The behavior of these utilities is affected by assignment of the
mem authorization On systems installed with ``high'' security,
this is usually reserved for system administrators. If you do not
have this authorization, the output will be restricted to data
about your activities. Refer to ``Using a secure system'' in the
Operating System User's Guide for more details.
---snip---
So, for me, setting up w in asroot with root privs, and adding w authorization to a user, and having that user run "/tcb/bin/asroot w" made no difference, but perhaps on your box it will. All my boxes are installed with the default security.
You may want to do the same with ps.
--
Brian K. White brian@xxxxxxxxx http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!
.
- References:
- Re: user permission problems
- From: andrewm659@xxxxxxxxx
- Re: user permission problems
- From: Nico Kadel-Garcia
- Re: user permission problems
- Prev by Date: Re: Working Emacs compilation for OR 5.0.6 after security updates?
- Next by Date: Re: help analyzing low system(with sar/vmstat/u386mon/sarcheck data)
- Previous by thread: Re: user permission problems
- Next by thread: Re: user permission problems
- Index(es):
Relevant Pages
|
|