Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!spool.mu.edu!snorkelwacker.mit.edu!hsdndev!cmcl2!panix!eravin From: eravin@panix.uucp (Ed Ravin) Newsgroups: comp.unix.aix Subject: Re: Using ksh set -u breaks xinit script... Message-ID: <1991Mar29.173129.20779@panix.uucp> Date: 29 Mar 91 17:31:29 GMT References: <1991Mar28.012949.1375@arnor.uucp> <1991Mar28.153242.8791@panix.uucp> <1991Mar28.191007@ibmpa.awdpa.ibm.com> Organization: Unix Sezchuan Enlightment Team Lines: 25 In article bob@ibmpa.awdpa.ibm.com (Bob Andrews) writes: >You might also try changing the first line of the xinit script to: > >#! /bin/ksh -p > >I haven't tried this, so it may introduce other errors, but it should prevent >the ksh from looking at your .profile, etc. files... Hmmm. This is the first system I've used that uses ksh as its default shell, so the system scripts are picking up my .kshrc. Considering the level of customization possible in ksh, and considering what some people do to their environments, it's probably wise for all system scripts to insist upon using only inheriting environment variables and not shell aliases or option settings. Since my last posting, I've discovered the "info" script also likes to reference uninitialized variables. Then again, the Info Explorer interface from an ASCII terminal is so dismal that I'm not sure I care... -- ---------------------------------------------------------------------------- Ed Ravin | Even if I could think of a profound, witty, insightful cmcl2!panix!eravin | quote to put here noone would bother reading it. philabs!trintex!elr |