Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!uflorida!haven!mimsy!mojo!stripes
From: stripes@eng.umd.edu (Joshua Osborne)
Newsgroups: comp.windows.x
Subject: Re: xterm, xload, and X libraries in non-standard locations
Message-ID: <1990Mar14.010418.14053@eng.umd.edu>
Date: 14 Mar 90 01:04:18 GMT
References: <9003061606.AA17990@nswc-wo.arpa> <ZS-##4=@rpi.edu> <22078@metropolis.super.ORG>
Sender: news@eng.umd.edu (The News System)
Organization: Maryversity of Uniland, College Park
Lines: 14

In article <22078@metropolis.super.ORG> rminnich@metropolis.UUCP (Ronald G Minnich) writes:
>In article <ZS-##4=@rpi.edu> tale@cs.rpi.edu (David C Lawrence) writes:
>no, if you make them sgid kmem it fails too.
>How do you get full functionality out of xload if you
>can't read kmem? Or do you make kmem world-readable? 
>I don't get it.
If you staticly link xload then it doesn't need any shared libs, so it doesn't
matter that it only searches the standard path, because all it needs is libc.so!
-- 
           stripes@eng.umd.edu          "Security for Unix is like
      Josh_Osborne@Real_World,The          Mutitasking for MS-DOS"
      "The dyslexic porgramer"                  - Kevin Lockwood
"Don't try to change C into some nice, safe, portable programming language
 with all sharp edges removed, pick another language."  - John Limpert