Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!panews.awdpa.ibm.com!ibmpa.awdpa.ibm.com!bob From: bob@ibmpa.awdpa.ibm.com (Bob Andrews) Newsgroups: comp.unix.aix Subject: Re: Using ksh set -u breaks xinit script... Message-ID: <1991Mar28.191007@ibmpa.awdpa.ibm.com> Date: 29 Mar 91 03:10:07 GMT References: <1991Mar26.051930.16308@panix.uucp> <1991Mar28.012949.1375@arnor.uucp> <1991Mar28.153242.8791@panix.uucp> Sender: news@ibmpa.awdpa.ibm.com (news id) Reply-To: bob@ibmpa.awdpa.ibm.com (Bob Andrews) Organization: IBM Advanced Workstations Division, Palo Alto Lines: 23 In article <1991Mar28.153242.8791@panix.uucp>, eravin@panix.uucp (Ed Ravin) writes: |> In article prener@prener.watson.ibm.com (Dan Prener) writes: |> >If all uses of undefined shell variables are to be considered errors, |> >then it becomes very difficult to get first-time switches and to |> >keep other state. |> |> It's not at all difficult. The first time you reference any shell variable, |> you can specify a value to be used instead if the variable is not set or a |> value to assign it to if the variable is not set. For example: |> 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... -- --- Bob Andrews UNIX: bob@ibmpa.awdpa.ibm.com VNET: BANDREWS at AUSTIN (if you must)