[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

19990122: dchrly

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 19990122: dchrly
  • Date: Fri, 22 Jan 1999 12:19:00 -0700
Frank,

You may need to ensure that you are indeed running a csh and not
a ksh, sh, bash, or some other shell. File redirection in
different shells uses different methods, however if your
command line looks like:
cat raw_metar.file | dchrly etc.
then the piping should not be affected by the shell interpretation
of the "<" character.

at your command prompt, typing echo $SHELL shoule respond /bin/csh.
Then, if you are running acsh, you should also verify that the first
line of your comm script is:
#/bin/csh

Without the above first line, the comm script will be executed
using sh instead of csh. Typing "csh comm" will force the
script to be executed by csh.

Feel free to send me anything you have in a script for me to
look at.

Steve Chiswell

>From: "Frank Colby" <address@hidden>
>Organization: University of Massachusetts Lowell
>Keywords: 199901221854.LAA23020

>Steve
>
>Thanks for trying to make sense of my mess.  In the pqact.conf, I use
>explicit file designations, but I just checked and indeed, although
>dchrly is given world x access, the packing files are not, nor are the
>station id tables.  Hence the program tries to execute and cannot do
>anything.  That will probably take care of the automatic process.
>
>The script problem is a little different.  If I type the dechrly
>command, it comes out as very long, with the -d, -p and -s options
>referring to very long file descriptions.  If I just type it outright to
>the screen, the command doesn't seem to work, but if I put \cr after
>each section, it works fine.
>
>The problem is that when I try to execute this from a script, it doesn't
>work.  I have even echoed the command from the script, and then run it
>using the \cr to break up the pieces directly, and that works.  But if I
>just use a line like
>
>$comm
>
>where comm is the full command, dchrly just sits there, as though it is
>input file part.
>
>I tried to insert the \cr into the script, to see if that would make any
>difference but the \ works differently when in a script and output using
>the $.
>
>So, if you have any ideas, I would be thrilled.  I would be happy to
>send you screen captures and the script if that would help.
>
>Frank
>