home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!swrinde!sdd.hp.com!caen!batcomputer!lynx.msc.cornell.edu!ransom.msc.cornell.edu!rick
- From: rick@ransom.msc.cornell.edu (Rick Cochran)
- Newsgroups: comp.unix.aix
- Subject: 'limits' in xdm login sessions
- Keywords: AIX 3.2 xdm limits
- Message-ID: <1992Jul23.170739.29773@msc.cornell.edu>
- Date: 23 Jul 92 17:07:39 GMT
- Sender: news@msc.cornell.edu
- Organization: Cornell Materials Science Center
- Lines: 30
-
- Some of you may have noticed that your 'limits' are different, depending
- on whether your session originates with 'xdm' or not. In our case, we
- cannot run the 1.2.0.6 version of xlc in an 'xdm' originated session.
-
- As someone VERY helpfully pointed out when I inquired about this before,
- this is a result of the fact that 'xdm' is started in rc.local which is
- started by the 'init' process which does not have the same 'limits' as,
- for example, a 'root' login session.
-
- The method they suggested was to hack xdm to call 'setpcred' to set the
- process credentials for xdm sessions. This is doable, but requires
- adding an argument to a function call and is somewhat messy.
-
- Another way to eliminate the problem is to use the following rc.local lines to
- invoke xdm:
-
- if [ -f /usr/bin/X11/xdm -a -f /usr/local/xdm/xdm-config ] ; then
- su root "-c /usr/bin/X11/xdm -config /usr/local/xdm/xdm-config"
-
- This will cause all xdm sessions to get the same limits as root, which is
- fine in our case.
-
- Just out of curiosity, is 'setpcred' an IBM invention? I try to keep
- a positive attitude toward deviations from 'standard Unix' (whatever
- that is), but they do result in a certain amount of pain and boredom.
-
- --
- |Rick Cochran 607-255-7223 rick@msc.cornell.edu|
- |Cornell Materials Science Center rick@crnlmsc2.bitnet|
- |E20 Clark Hall, Ithaca, N.Y. 14853 cornell!msc.cornell.edu!rick|
-