HDTenEightyP/NetNews huggingface dataset:
From: zhu@controls.ccd.harris.com (Gary Zhu)
Subject: Re: How to redirect outputs from the command "time" into a file? 
Originator: zhu@rs2
Organization: Harris Controls
Date: Fri, 6 Nov 1992 23:14:10 GMT


In article <fish.720983465@news2.gsfc.nasa.gov>, fish@daacdev1.stx.com writes:
|> mt0lamg@convex1.tcs.tulane.edu (Louis X. Lee) writes:
|> 
|> >My first question is about saving outputs from the timing command
|> >"time" into a file. I tried "time a.out > a.time", but it did not
|> >work. How to capture the outputs into a file?
|> time puts its output on stderr (not noted in any man page i've
|> ever seen either) so:
|> time a.out 2>a.time
|> 
|> 			fish
|> --
|> John R. Vanderpool                INTERNET: fish@daacdev1.stx.com
|> NASA/GSFC                         VOX: 301-513-1683                
|> Hughes/STX Corporation            FAX: 301-513-1608
|> "somehow seems strange and a little bit funny, to wander thirsty in the rain" pr

Almost got it.

"time"  will consider the rest of the line as a whole, so

time a.out 2>a.time

will be interpreted as :  run  "a.out 2>a.time"  and report the
running time of "a.out 2>a.time".


SOLUTION :    (time  a.out) 2>a.time

                                     Gary
Xref: sparky comp.unix.shell:4576 comp.unix.programmer:5187 comp.unix.wizards:4554
From: smr@pki-nbg.philips.de (Stephen Riehm)
Newsgroups: comp.unix.shell,comp.unix.programmer,comp.unix.wizards
Subject: Re: optarg(1) and quoted args, help wanted.
Date: 6 Nov 92 15:04:29 GMT
Reply-To: smr@pki-nbg.philips.de

> I am trying to use getopt(1) in some /bin/sh scripts to parse the
> command line options, it works fine, except I want to get around
> something that we are warned against in the manpage, namely embedded
> blanks in args.

> for example:
> command -abc 'comment which might be long' -de file ...

In response to the huge number of replies that I have received on this
topic, here is a summary:

1. use getopts(1) if it is available.
2. there are various hacks to get the shell to interpret the output
    from getopt(1), none are especially neat however, and with most you
    would be just as well off if you simply threw out getopt all
    together.
3. Write your own... which is exactly what I did. While I was at it I
    added some extra functionality, while maintaining backward
    compatibility. An offshoot of this was that I ended up with code
    for my own version of getopt(3), with the extra functionality.
    Basically the extra functionality is that you can specify options
    which may be prefixed by a + aswell as a -, (normally +<opt> gives
    you an error), and the addition of a -q and -c option to
    getopt(1). -q puts quotes around args with white space, and -c can
    be used to specify the name of the command to print in the event
    of errors, so that instead of running a shell and getting:
	getopt: Illegal option -- q
    you can now get
	my_cmd: Illegal option -- q
    OK, they're minor changes, but they help to make the world a nicer
    place.

If anyone is interested in a copy of my re-invented wheel, drop me a
line and I'll send you a shar file (16kb).
(PS: I haven't got around to make a manpage for it yet, but there's
lotsa of comments to keep you busy)

thanks to all those who replied!

-----------------------------------------------------------------
Stephen Riehm		Configuration Management	   _-_|\ 
smr@pki-nbg.philips.de	Philips Kommunikations Industrie  /     \
Work: +49 911 526 2975	N|rnberg, Germany		  \_.-.*/
Fax:  +49 911 526 3678	"I was there, now I am here!"	       v 
"My company speaks another language, I CAN'T speak on its' behalf"
From: eddjp@dinowine.huber.com (Dewey Paciaffi)
Newsgroups: comp.unix.shell
Subject: Am I writing to a tty or pipe?
Date: 12 Nov 92 18:25:37 GMT
Organization: J.M. Huber Corp, Edison, NJ


Is there a way to determine from within a Bourne shell script if
the output is being written to a tty or a pipe?
From: chet@odin.ins.cwru.edu (Chet Ramey)
Newsgroups: comp.unix.shell
Subject: Re: How to quote '~' in Zsh?
Date: 9 Nov 1992 20:22:30 GMT
Organization: Case Western Reserve University, Cleveland OH (USA)
NNTP-Posting-Host: odin.ins.cwru.edu

>'~' and "~" also expands to my homedir.

This is, in my opinion, a bug.  At least one of them should serve
to inhibit tilde expansion.  Posix.2 says both should work.  (Yes,
I realize that zsh does not implement Posix.2.)

Chet
-- 
``The use of history as therapy means the corruption of history as history.''
	-- Arthur Schlesinger

Chet Ramey, Case Western Reserve University	Internet: chet@po.CWRU.Edu
From: ttn@cs.tut.fi (Tero Nieminen)
Newsgroups: comp.unix.shell
Subject: Re: suicidal kill command ?
Date: 6 Nov 92 02:40:42 GMT
	<1992Oct31.192155.3021@nic.csu.net
	<1992Nov3.022415.12993@athena.cs.uga.edu>
Organization: Tampere Univ. of Technology, Finland.
NNTP-Posting-Host: sepelrastas.cs.tut.fi
In-reply-to: david@marie.stat.uga.edu's message of Tue, 3 Nov 1992 02:24:15 GMT

In article <1992Nov3.022415.12993@athena.cs.uga.edu> david@marie.stat.uga.edu (David Gundlach) writes:

   I don't know of a way to actually make kill do this by itself, but
   I've whipped up a 'kp' script (originally for 'kill program') that
   does the job.  And after all, aren't you suppposed to build new tools
   out of existing ones? ;-)

   Here it is, a one-line shell script:

   echo "Killing '$1' processes..."; kill $2 `ps -agux | grep $1 | sort | awk '{print $2}'`

One useful thing to chek is "which kill". It might say "kill: shell
built-in command". In that case you have to use another kill for the job
(ie. /bin/kill -9 -1). That does the tric on machines over here.

At least csh/tcsh users should watch out for this..
--
     Tero Nieminen                 Tampere University of Technology
     ttn@cs.tut.fi                     Tampere, Finland, Europe
From: micah@hardy.u.washington.edu (Micah Anderson)
Newsgroups: comp.unix.shell
Subject: How to interpret when the end of piece of mail is reached?
Summary: does mail have some sort of delimetewr?
Keywords: mail, sh, script
Date: 8 Nov 92 20:59:09 GMT
Article-I.D.: u.1992Nov8.205909.21877
Organization: University of Washington

How can I tell where one message ends in mail and where one begins?
There isn't any obvious delimeter when I cat my mailbox...
From: kuro@vodka.Eng.Sun.Com (Teruhiko Kurosaka)
Newsgroups: comp.unix.shell
Subject: how to get the last pos. parameter in ksh?
Date: 9 Nov 92 17:26:43 GMT
Reply-To: kuro@Eng.Sun.Com
Organization: SunSoft, a Microsystems company, Mt.View, CA, USA
NNTP-Posting-Host: vodka

How can I write a ksh function to examine the last parameter (argument)
of the command line?  I.e., I'd like to know how to access argv[argc-1].
I tried:
	${$#}
but this was interpreted as ${$} yielding the process id of the shell.
Another try:
	${@[${@#}]}
gave me a syntax error.
-kuro
--
-------
T. Kurosaka ("Kuro") --- SunSoft, a Sun Microsystems company
Internet:kuro@Eng.Sun.Com Voice:+1 415 336-5284 Fax:+1 415 336-6015
US Mail: Mail Stop MTV5-44, 2550 Garcia Ave., Mt. View, CA 94043-1100 USA
Xref: sparky comp.unix.shell:4543 comp.lang.misc:3493
From: peter@ferranti.com (peter da silva)
Newsgroups: comp.unix.shell,comp.lang.misc
Subject: Re: Need script (awk/sed/...) to remove dashes and do initial caps
Date: 4 Nov 92 18:11:24 GMT
Article-I.D.: ferranti.id.K_OU.BLD
Organization: Xenix Support, FICC

In article <1992Nov2.195646.27860@spectrum.xerox.com> kris.wbst129@xerox.com writes:
> Here are some examples of what needs to be done:
> 
> hello-world => HelloWorld
> helloworld => Helloworld
> HELLOWORLD => Helloworld
> HELLO-WORLD => HelloWorld

Here's a LEX program to do it.

%START WORD
%%
[A-Za-z]+ { trans(yytext, yyleng); BEGIN WORD; }
<WORD>\-[A-Za-z]+ { trans(&yytext[1], yyleng-1); BEGIN WORD; }
.	{ ECHO; BEGIN 0; }
\n	{ ECHO; BEGIN 0; }
%%
#include <ctype.h>

trans(s, l)
char *s;
int l;
{
	int i;

	output(toupper(s[0]));
	for(i = 1; i<l; i++)
		output(tolower(s[i]));
}
-- 
% Peter da Silva % 77487-5012 % +1 713 274 5180 % Har du kramat din varg idag?
/M{moveto}def/H{newpath 0 19 M 0 6 R 4 -4 R 0 16 M 5 0 R 3 -3 R -4 0 R -3 3 R 8
8 M 0 5 R stroke}def/R{rlineto}def 24 24 scale 3 3 translate H newpath 10 6 M 2
2 R -4 0 R closepath stroke 20 0 translate -1 1 scale H showpage %    `-_-'
Newsgroups: comp.unix.shell
From: kherron@ms.uky.edu (Kenneth Herron)
Subject: Re: C-Shell question
    <1992Nov4.080338.9458@eua.ericsson.se> 
    <1992Nov5.020850.572@news.csd.sgi.com> 
    <1992Nov6.115704.23205@cs.utwente.nl>
Distribution: na
Date: Fri, 6 Nov 1992 16:39:10 GMT
Organization: University Of Kentucky, Dept. of Math Sciences

ahoekstr@cs.utwente.nl (Andre D. Hoekstra) writes:

>>The exit status you get is from the command "rsh" and not from the script it
>>executes. Since "rsh" completes normally, you will see "0" which is its 
>>"completion ok" status. If you do an "echo $status" inside the script, you
>>might see the exit status of the command of rm.

>The original question was:

>I have a script that goes:

>#!/bin/csh # ??

>/bin/rm -f file

>if ( $status ) then blabla

>#end of script; exit

>When I run this script normallly it works OK, but when I try to
>rsh somehost script
>I always get a $status of 0

No, this *wasn't* the original question.  In the original question,
the rm command line didn't have the -f option.  This makes a *lot*
of difference.  On at least the two systems I tried here, rm -f
always results in a 0 exit code no matter how many files rm was able
to remove.  I suspect the answer to your question is simply that rm 
works differently on the system you're rsh'ing to.

Let me suggest that in the future you include the actual script--edit
out the irrelevant parts if it's big--rather than retyping it in your
post.

As for Mr. Vidya and the others, it sounds like they didn't read your
question closely enough and thought you were doing something like

	#! /bin/csh
	rsh foo /bin/rm file
	if ( $status ) ...

-- 
Kenneth Herron                                              kherron@ms.uky.edu
University of Kentucky                                         +1 606 257 2975
Dept. of Mathematics     "Your ball goes over them, it sails off the edge into
a huge cauldren of fire-breathing dragons."  "And they call this a par three?"
Newsgroups: comp.unix.shell
From: boyd@prl.dec.com (Boyd Roberts)
Subject: Re: How to interpret when the end of piece of mail is reached?
Keywords: mail, sh, script
Organization: Digital Equipment Corporation - Paris Research Laboratory
Date: Sun, 8 Nov 1992 21:44:58 GMT

In article <1992Nov8.205909.21877@u.washington.edu>, micah@hardy.u.washington.edu (Micah Anderson) writes:
> How can I tell where one message ends in mail and where one begins?
> There isn't any obvious delimeter when I cat my mailbox...

The delimeter is a line that begins with:  From<space>

Don't even think of following up with some theory that is based around
four control-A's.  Only brain-damaged user agents do that.


Boyd Roberts			boyd@prl.dec.com

``Not only is UNIX dead, it's starting to smell really bad.''  -- Rob Pike
Newsgroups: comp.unix.shell,comp.unix.sysv386
From: gary@sci34hub.sci.com (Gary Heston)
Subject: Re: Does *anyone* know of a GOOD shell  for Sysv 3.2? (w command line editing)?
Reply-To: gary@sci34hub.sci.com (Gary Heston)
Organization: SCI Systems, Inc., Huntsville, Al.
Date: Fri, 13 Nov 1992 22:29:04 GMT

In article <BxMDDy.H5M@ernest.itg.ti.com> alan@ernest.itg.ti.com (Alan Edmonds) writes:

>  [ ... ]  Works real well for me.  I'm not sure you would want 
>roots shell as tcsh.    I'm using it on ISC 2.2.1 and SunOS 4.1.x.

Neither you, nor anyone else. Don't ever use anything other than /bin/sh
for the root login on a SysV system. Sort of interferes with the boot
scripts working properly, among other things.

-- 
Gary Heston    SCI Systems, Inc.  gary@sci34hub.sci.com   site admin
The Chairman of the Board and the CFO speak for SCI. I'm neither.
"Data sheet: HSN-3000 Nuclear Event Detector. The [NED] senses the gamma
radiation pulse [from a] nuclear weapon." As if we wouldn't notice...
Newsgroups: comp.unix.shell
From: fsjean@godiva.lerc.nasa.gov (Jeannine Banks)
Subject: Sample Shell Scripts
Organization: NASA Lewis Research Center [Cleveland, Ohio]
Distribution: usa
Date: Mon, 9 Nov 1992 13:10:54 GMT

>Article 7761 (69 more) in comp.unix.shell:
>From: htewari@cs.tcd.ie (Hitesh Tewari)
>Subject: Sample Shell Scripts
>Organization: Computer Science, Trinity College Dublin
>Date: Tue, 3 Nov 1992 14:48:43 GMT
>Lines: 11

>Hi,
>        I am trying to learn how to write shell scripts(csh). If you have any
>scripts that well documented then can you please mail them to me. It
>does not matter what the purpose of the script is as long as it has a
>few comments, and will give me an idea of how to write an efficient
>script. 

>If anyone has a list of all the frequently used commands, then can you 
>send then to me as well. Thanks in advance.

>Hitesh

Hello,

I am also trying to learning shell programming.  If anyone has sample
shell scripts please, send.  Thank you.

Jeannine Banks

-- 
*************************************************************   
*Jeannine Banks            ** Phone Number:  (216) 433-8538* * O .
*Sverdrup Technology, Inc. ** Mail Stop 5-11               *  *  o  _///_ //
*NASA Lewis Research Center** Workstation Administrator     *   *  <`)=  _<<
*            ** Email:  fsjean@godiva.lerc.nasa.gov **     *  *      \\\  \\
**************************************************************
                 HAVE A NICE and ENJOYABLE DAY!!!!!!
From: micah@carson.u.washington.edu (Micah Anderson)
Newsgroups: comp.unix.shell
Subject: New mail?
Summary: How to find out if I have new mail?
Keywords: mail, csh
Date: 6 Nov 92 06:33:34 GMT
Organization: University of Washington

How can I find out if I have new mail and when I do run my shell script?
I cannot use .filter, so would something like:

test -s /usr/spool/mail/$USER
if (status == 0) then
script
endif

would this be a good idear? (adding in a sleep and then running it again..)

any suggestions?
Newsgroups: comp.unix.shell
From: coy@guinness.NoSubdomain.NoDomain (Coy Correll)
Subject: Re: echo question
Organization: Dazix - An Intergraph Company
Date: Tue, 10 Nov 1992 14:04:36 GMT

In article <1992Nov9.171618.5675@midway.uchicago.edu>, a-douglas@uchicago.edu (Allen Douglas) writes:
|> I would like to echo tab and line return characters to the screen and/or 
|> understandto a file. But I must not the escaping/quoting mechanism.  According
|> to my UNIX reference I should be able to type:
|> 
|> quads% echo Bob'\t\t'cat
|> and get:
|> Bob        cat
|> 
|> unfortunately I get:
|> quads% echo Bob'\t\t'cat
|> Bob\t\tcat
|> 
|> What  gives?  Thanks in advance!

The syntax you are using is for sys5 only.   If you are on a
sparcstation, you can type /usr/5bin/echo to get the desired
results.  This is fully explained in the man page for echo 
on sparcstations.

|> 
|> Allen

-- 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Coy Correll                      e-mail: ccorrell@dazixco.ingr.com
Intergraph                     my phone: (303) 581-2389
6095 Spine Road                     fax: (303) 581-9972
Boulder, Colorado 80301   company phone: (303) 581-2300
From: htewari@cs.tcd.ie (Hitesh Tewari)
Newsgroups: comp.unix.shell
Subject: Documentation on awk/gawk
Date: 13 Nov 92 18:53:55 GMT
Organization: Computer Science, Trinity College Dublin

Hi,
	Just found some very interesting material on gawk, which is the
gnu equivilant of awk. It is called "The Gawk Manual" and can be
obtained from "mcsun.eu.net"(192.16.202.1) by anonymous ftp. It's in
postscript format in /gnu/gawk . The authors say that gawk is fully
compatible with awk with added features. By the way the binaries for
gawk are there if you're system does not already have them.

Hitesh
Newsgroups: comp.unix.shell
From: dkeisen@leland.Stanford.EDU (Dave Eisen)
Subject: Re: How to redirect outputs from the command "time" into a file? 
Organization: Sequoia Peripherals, Inc.
Date: Sat, 7 Nov 92 18:44:11 GMT

In article <1992Nov6.231410.28155@ccd.harris.com> zhu@controls.ccd.harris.com (Gary Zhu) writes:
>
>In article <fish.720983465@news2.gsfc.nasa.gov>, fish@daacdev1.stx.com writes:
>|> 
>|> time puts its output on stderr (not noted in any man page i've
>|> ever seen either) so:
>|> time a.out 2>a.time

>Almost got it.
>"time"  will consider the rest of the line as a whole, so
>time a.out 2>a.time
>will be interpreted as :  run  "a.out 2>a.time"  and report the
>running time of "a.out 2>a.time".
>
>SOLUTION :    (time  a.out) 2>a.time

Fish was right. Assuming a Bourne-like shell (he did use the 2>a.time
Bourne syntax), time couldn't possibly report the running time of the
redirected command because the redirection would occur before /bin/time
was called.

Of course, all of this changes if time is a shell builtin, like it
is in csh and tcsh and probably some others. Then time can (and in 
the case of csh does) time the redirected command and your answer
would be correct if csh used the 2>a.time syntax for redirection.



-- 
Dave Eisen                               Sequoia Peripherals: (415) 967-5644
dkeisen@leland.Stanford.EDU              Home:                (415) 321-5154
       There's something in my library to offend everybody. 
          --- Washington Coalition Against Censorship
Newsgroups: comp.unix.shell
From: a-douglas@uchicago.edu (Allen Douglas)
Subject: echo question
Organization: U of C  Law School
Date: Mon, 9 Nov 1992 17:16:18 GMT

I would like to echo tab and line return characters to the screen and/or 
understandto a file. But I must not the escaping/quoting mechanism.  According
to my UNIX reference I should be able to type:

quads% echo Bob'\t\t'cat
and get:
Bob        cat

unfortunately I get:
quads% echo Bob'\t\t'cat
Bob\t\tcat

What  gives?  Thanks in advance!

Allen
From: alan@ssd.ukpoit.co.uk (Alan Barclay)
Newsgroups: comp.unix.shell
Subject: Re: How to interpret when the end of piece of mail is reached?
Keywords: mail, sh, script
Date: 12 Nov 92 16:02:32 GMT
Organization: iT - The Information Technology Business Of The Post Office

In article <1992Nov8.214458.17317@prl.dec.com> boyd@prl.dec.com (Boyd Roberts) writes:
>In article <1992Nov8.205909.21877@u.washington.edu>, micah@hardy.u.washington.edu (Micah Anderson) writes:
>> How can I tell where one message ends in mail and where one begins?
>> There isn't any obvious delimeter when I cat my mailbox...
>
>The delimeter is a line that begins with:  From<space>
>
>Don't even think of following up with some theory that is based around
>four control-A's.  Only brain-damaged user agents do that.

So when I have a message like this one, which has been split up by
some ignorant user putting something supid, but reasonable eg:

From Henry the eighth's time onwards, the English Established church,
the Church of England, has allowed divorce.

Then this is now a new message?? Sorry, I think that the unusal
sequence of control codes is much better than the looking for an
usual sequence of printable letters.


-- 
Alan Barclay, iT, Barker Lane, CHESTERFIELD, S40 1DY, Derbys, England 
alan@ukpoit.uucp, ..!uknet!ukpoit!alan, FAX:+44 246214353, VOICE:+44 246214261
iT - The Information Technology Business     | explist now set to 3 days.
Of The Post Office : In Tune With Technology | Anyone got a 1.2 Gig disk?
Newsgroups: comp.unix.shell
From: s4uhkm@fnma.COM (Howie Michalski)
Subject: Re: setting the output of awk
Reply-To: s4uhkm@fnma.COM
Organization: Fannie Mae
Date: Fri, 13 Nov 1992 20:38:51 GMT

In article 10150@u.washington.edu, micah@carson.u.washington.edu (Micah Anderson) writes:
>How can I set the variable I am selecting with awk to a shell variable??
>Or would this be better done in sed?
>
>for example:
>
>grep ^Subject: $MBOX|awk '{$2}'|=Subject
>
>I want to take the subject from my mail and ake it so I can act upon it
>within shell (|=Subject does not work, btw)


Try:

csh -   set VARIABLE =  `grep ^Subject: $MBOX|awk '{$2}'|=Subject`

 sh -  VARIABLE=`grep ^Subject: $MBOX|awk '{$2}'|=Subject`

Cheers,
Howie
---
#include <std_disclaimer.h>                /* Howard Michalski    */
#define OPINIONS "My own"                  /* howie@fnma.COM      */
                                           /* Fannie Mae          */
main()/*iac*/{for(;/*hire*/;);}            /* Washington, DC, USA */
From: guy@Auspex.COM (Guy Harris)
Newsgroups: comp.unix.shell
Subject: Re: The Problem with UNIX
Date: 12 Nov 92 01:11:40 GMT
Organization: Auspex Systems, Santa Clara

> Mike> Things that bother me about the command line (I'm using Motorola
> Mike> UNIX System V/68 Release 3.71 running a Korn shell using vi-type
> Mike> command line editing on a VT420), in no particular order:
>
> Mike> 1) It is possible to backspace over the prompt.
>
>Get BSD tty drivers or tcsh.

Or learn EMACS and use EMACS-type command-line editing. :-)

If "ksh" does "vi"-style command-line editing in cooked mode, changing
the tty driver - e.g., by getting SVR4, with a SunOS 4.x-derived
"ldterm" that *does* properly handle the erase character, and won't let
you backspace over the prompt - will help.

If "ksh" does "vi"-style command-line editing in uncooked mode, it's a
bug in "ksh" if it lets you backspace over the prompt.

("ksh" does EMACS-style command-line editing in uncooked mode.)
Newsgroups: comp.unix.shell
From: boyd@prl.dec.com (Boyd Roberts)
Subject: Re: RM LOGIC
Organization: Digital Equipment Corporation - Paris Research Laboratory
Date: Fri, 6 Nov 1992 13:23:32 GMT

In article <1559@rand.mel.cocam.oz.au>, twp@rand.mel.cocam.oz.au (Tony Payne CSD) writes:
> 
> Nor have I ever seen a UNIX beastie like that. It seems to boil down to the
> fact that most files don't ever have their inode changed, except when they are
> created. So in most cases inode change time corresponds to creation time.
> Just another idiotic historical hangover.
> 

Well it always good to add more noise into the signal.  The inode change
time changes when the inode data changes.  Most of the time this occurs
on writes, but also ocurrs on chmod, chown etc but they are probably
less frequent.  So the ctime would indicate a files creation time in
this one case alone:  a file that has only had creat operations.

So, you want an example:

    prl313 ; work/sheraton/walk hosts
    721054655 721054676 721054655 664 - hosts

What we see here is that the ctime and mtime are equivalent, whereas
the atime is somewhat later.  I clicked on write in `sam' at 721054655
and then read the file 21 seconds later at 721054676.


Boyd Roberts			boyd@prl.dec.com

``Not only is UNIX dead, it's starting to smell really bad.''  -- Rob Pike
Newsgroups: comp.unix.shell
From: calyx.corp <calyx.corp@mixcom.mixcom.com>
Subject: ksh alias export
Organization: Milwaukee Internet Xchange BBS, Milwaukee, WI U.S.A.
Distribution: usa
Date: Fri, 06 Nov 1992 00:07:38 GMT


How can you export aliases in the korn shell to a subshell
that is created with ksh.   I tried some tricks with the 
SHELL environment variable and to no avail.  
Thanks in advance for any help.
Tom Feller

-- 
calyx.corp@mixcom.com