sanders@peyote.cactus.org (Tony Sanders) (02/20/91)
In article <1991Feb19.182028.7164@dartvax.dartmouth.edu> paw@eleazar.dartmouth.edu (Pat Wilson) writes: >Why doesn't lsps -a report the correct paging %Used to non-root users? >It also indicates that the space isn't active... Did I miss something >in info that would have told me I need to su to see how close I'm >coming to SIGDANGER? lsps -a workes ok at: Option Name State Event Date/Time Release User Name -------------------- ---------- ---------- --------- --------------- ---------- bos.obj INACTIVE COMMIT 02/02/90 03.01.0000.0000 root INACTIVE APPLY 12/31/69 03.01.0003.0013 root ACTIVE COMMIT 12/31/69 03.01.0003.0013 root I've seen it work incorrectly at older levels. Also, I think you might want to checkout the psdanger() subroutine. -- sanders@peyote.cactus.org First rule of software: Throw the first one away. and so on... I am not an IBM representative and I speak only for myself.
jfh@greenber.austin.ibm.com (John F Haugh II) (02/21/91)
In article <1991Feb20.053754.1669@engin.umich.edu> wross@caen.engin.umich.edu (Wendy Ross) writes: >Either one of the above might be worth reporting to IBM to see >if they'll change the permissions in future releases ... >Next time I decide I have a long enough list of things to >mention to IBM, I'll give these two a whirl and see what >they say. The problem was reported to the Level 3 support center last fall and was (presumably) fixed. I don't recall which level as I am no longer part of the group. But I do remember that someone in the group DID fix exactly what you describe. There is nothing wrong with making LSPS setgid or setuid to the appropriate group. I recall that the code does "the right thing" for various values of "the right thing". -- John F. Haugh II | I've Been Moved | MaBellNet: (512) 838-4340 SneakerNet: 809/1D064 | AGAIN ! | VNET: LCCB386 at AUSVMQ BangNet: ..!cs.utexas.edu!ibmchs!auschs!snowball.austin.ibm.com!jfh (e-i-e-i-o)