HDTenEightyP/NetNews huggingface dataset:
Newsgroups: comp.unix.shell,comp.unix.programmer
Subject: Re: Cron Script to check & auto-restart the died process periodically
From: oleg@gd.       (Oleg Kibirev)
Date: 17 Nov 92 00:10:47 PST
Organization: Computer Science Departement of California State University in Fresno

In article <1992Nov16.213830.25277@tamsun.tamu.edu> spatel@cs.tamu.edu (Samir K Patel) writes:
>
>
>  We have some system processes running in background to ingest the realtime
>  data from various ports. This processes are started at the boot time by
>  rc.local. 
>
>  Now some time this processes dies due to some errors in the data feed
>
>  So we need to periodically check that this processes are running and
>  if not we need to restart the process. I think cron can do it but I don't
>  know exactly how to check that process is running or not.
>
Why not having the process write /etc/smth.pid so that a script started in
crontab can do kill -0 PID to check if it's still alive?

Oleg

Newsgroups: comp.unix.shell,comp.unix.sysv386
From: nbladt@autelca.ascom.ch (Norbert Bladt)
Subject: Re: Does *anyone* know of a GOOD shell for Sysv 3.2? (w command line editing)?
Organization: Ascom Autelca AG, Guemligen, Switzerland
Date: Mon, 16 Nov 1992 15:22:09 GMT

feoh@hal.gnu.ai.mit.edu (Chris Patti) writes:

>Hello. I use/administer a number of PC based System V 3.2 systems, and the 
>standard Bourne shell is driving me mad with its lack of command line editing
>capabilities..

I can imagine that you are desperate. I had to use the csh for a few days
(on 386BSD) and I finally found the zorn-shell (zsh).
I don't know how easy this is to port to SysV-ish systems, though.
But, there is a cure for your desperation, anyway.

We are using the korn-shell (ksh) on our Interactive 3.2 Rel. 2.2.1 system
without any problems.
You should get it (if you can afford it). I am not sure how we got it, but
we have it and it works well.

Norbert.
-- 
Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt
Newsgroups: comp.unix.shell
From: SEB1525@MVS.draper.com (Steve Bacher)
Subject: Re: mail (was: The Problem with UNIX)
Organization: Draper Laboratory
Date: Tue, 17 Nov 1992 23:28:00 GMT

In article <Bxr5BA.5G5@mudos.ann-arbor.mi.us>,
mju@mudos.ann-arbor.mi.us (Marc Unangst) writes:

>>~tilde 
>
>Well, of course.  If you don't like "~" being the escape character,
>change it to something else.  Or type it to an editor instead of
>mail's builtin text-collector.  Or type it directly to
>/usr/lib/sendmail.  (Of course, then you won't be able to edit your
>prose, but I suppose you don't want to...)

I don't want to. I'm not talking about being in an editor.  I'm talking
about automagically feeding a file to the mailer, possibly in a shell
script.  Yes, using sendmail with the proper bouquet of flags will do
most of this, except for...

>>From time immemorial
>
>This is a problem with the MTA on the receiving system.  Get one that
>knows about Content-Length: or uses something other than From_ to
>delimit messages, and you'll be fine.

Any suggestions?  You're talking about replacing sendmail with
something else.  If I'm just a lowly user on a machine owned by
somebody else who can't be bothered with replacing sendmail with
something else, what recourse do I have?

>>.
>
>A clear configuration problem with your MUA.  You need to turn on the
>"nodot" flag, or get a different MUA.

True.

--
Steve Bacher (Batchman)                 Draper Laboratory
Internet: seb@draper.com                Cambridge, MA, USA
Newsgroups: comp.unix.shell,comp.unix.programmer
From: mjl@bos.locus.com (Mike Leibensperger)
Subject: Re: Cron Script to check & auto-restart the died process periodically
Organization: Locus Computing Corp., Boston Massachusetts USA.
Date: Wed, 18 Nov 1992 15:46:14 GMT

In article <1992Nov16.213830.25277@tamsun.tamu.edu> spatel@cs.tamu.edu
(Samir K Patel) writes:

>    We have some system processes running in background to ingest the realtime
>    data from various ports. This processes are started at the boot time by
>    rc.local. 
>
>    Now some time this processes dies due to some errors in the data feed
>    So we need to periodically check that this processes are running and
>    if not we need to restart the process. I think cron can do it but I don't
>    know exactly how to check that process is running or not.

Mach has a program called nanny that is used to start daemons and
restart 'em when they croak.  Perhaps you could ftp the source from
C-MU and port it.  If restarting the processes *immediately* is not a
bit concern, you could ``kill -0 pid'' from a cron job as someone else
suggested.

>    Samir ( spatel@photon.cs.tamu.edu )

	yr obdnt svnt,	
	mjl



--
Michael J. Leibensperger      "Rats and roaches live by competition under the
Locus Computing/Boston		 laws of supply and demand; it is the privilege
25 Mall Road; Burlington MA	     of human beings to live under the laws of
01803 (617)229-4980 mjl@locus.com       justice and mercy."  -- Wendell Berry
Member of the League for Programming Freedom --- write league@prep.ai.mit.edu
Newsgroups: comp.unix.shell
From: etxmesa@eos.ericsson.se (Michael Salmon)
Subject: Re: Action of `echo */'
Reply-To: etxmesa@eos.ericsson.se (Michael Salmon)
Organization: Ericsson Telecom AB
Date: Thu, 19 Nov 1992 12:58:14 GMT

In article <1eg04jINN9go@sprocket.csv.warwick.ac.uk>
cudcv@csv.warwick.ac.uk (Rob McMahon) writes:
|> SunOS 4.1.3, tcsh 6.02.00, bash 1.12.1.
|> 
|> I was asked how to list just the subdirectories using ls, and said "easy, just
|> do `ls -d */'".  He was using tcsh, and it didn't work:
|> 
|> cudcv (2525) > \ls -F
|> xx/  yy*  zz/
|> cudcv (2526) > \ls -d */
|> xx/  yy/  zz/
|> cudcv (2527) > 
|> 
|> "Eek!" thought I, a bug in tcsh!, so just to check I tried csh:
|> 
|> cudcv (2527) > csh -c 'ls -d */'
|> xx/  zz/
|> cudcv (2528) > 
|> 
|> Fine.  "Hmm," I continued muttering to myself, "I wonder if bash has this
|> problem ?":
|> 
|> cudcv (2529) > bash -c 'ls -d */'
|> xx/  yy/  zz/
|> cudcv (2530) > 
|> 
|> Yes, it does.  sh ?
|> 
|> cudcv (2530) > sh -c 'ls -d */'
|> ls: */: No such file or directory
|> Exit 1
|> cudcv (2531) > 
|> 
|> Aagh!  Say what ?  I'm sure this used to work, in sh, csh, and tcsh.
|> Somewhere along the line it's all gone horribly wrong.  What's this crud from
|> tcsh and bash, and ls for that matter (/bin/ls and GNU ls behave the same).
|> Why won't /bin/sh expand `*/'.  `*/.' works in all cases of course.

SunOS 4.1.1, tcsh 6.02

 eos6 ~ 115 > /bin/ls -d */
C/          Wingz/      c/          ibm/        misc/       shql/
Calendar/   X11/        doc/        images/     motif/      sun/
MH/         apstools/   eXclaim/    include/    perl/       tmp/
Mail/       asa/        emacs/      incoming/   ps/         verilog/
News/       awk/        fig/        ipu21220/   rfc/        x/
SGML_docs/  b/          frame/      lib/        sc/         xview/
VILEARN/    bin/        hdl/        man/        shell/
 eos6 ~ 116 > ls-F -d */
C//          Wingz//      c//          ibm//        misc//       shql//
Calendar//   X11//        doc//        images//     motif//      sun//
MH//         apstools//   eXclaim//    include//    perl//       tmp//
Mail//       asa//        emacs//      incoming//   ps//         verilog//
News//       awk//        fig//        ipu21220//   rfc//        x//
SGML_docs//  b//          frame//      lib//        sc//         xview//
VILEARN//    bin//        hdl//        man//        shell//
 eos6 ~ 117 > ls -l lstest 
-rw-r--r--  1 etxmesa  z               0 Nov 19 13:53 lstest

bash and sh both refuse to expand */.

-- 

Michael Salmon

#include	<standard.disclaimer>
#include	<witty.saying>
#include	<fancy.pseudo.graphics>

Ericsson Telecom AB
Stockholm
Newsgroups: comp.unix.shell
From: SEB1525@MVS.draper.com (Steve Bacher)
Subject: Re: echo question
Organization: Draper Laboratory
Date: Tue, 17 Nov 1992 23:24:00 GMT

In article <17935@autodesk.COM>,
dansmith@Autodesk.COM (Daniel Smith) writes:

>In <19921114163004SEB1525@MVS.draper.com> SEB1525@MVS.draper.com (Steve Bacher) writes:
>
>> >        echo 'first:this=that=other+second:this=that=other+' | tr '=+' '\011\012'
>
>> Hardcoded octal ascii is "portable"???
>> Escaping syntax in tr is "portable"???
>
>        OK, name an english-language version of Unix this'll bomb on.

I haven't seen AIX/370, but I'm sure it'll bomb, being EBCDIC.

--
Steve Bacher (Batchman)                 Draper Laboratory
Internet: seb@draper.com                Cambridge, MA, USA
Newsgroups: comp.unix.shell,comp.unix.programmer
From: spatel@cs.tamu.edu (Samir K Patel)
Subject: Cron Script to check & auto-restart the died process periodically
Organization: Computer Science Department, Texas A&M University
Date: Mon, 16 Nov 1992 21:38:30 GMT



  We have some system processes running in background to ingest the realtime
  data from various ports. This processes are started at the boot time by
  rc.local. 

  Now some time this processes dies due to some errors in the data feed

  So we need to periodically check that this processes are running and
  if not we need to restart the process. I think cron can do it but I don't
  know exactly how to check that process is running or not.


  Samir ( spatel@photon.cs.tamu.edu )




Newsgroups: comp.unix.shell
From: mcook@fendahl.dev.cdx.mot.com (Michael Cook)
Subject: Re: Find and symbolic links
Organization: Motorola Codex, Canton, Massachusetts
Date: Mon, 23 Nov 1992 17:08:25 GMT

A. Satish Pai <Pai-Satish@CS.Yale.Edu> writes:

>I find it annoying that find doesn't follow links.

I think GNU find has a -follow directive.

Michael.
Newsgroups: comp.unix.shell
From: etxmesa@eos.ericsson.se (Michael Salmon)
Subject: Re: Find and symbolic links
Reply-To: etxmesa@eos.ericsson.se (Michael Salmon)
Organization: Ericsson Telecom AB
Date: Mon, 23 Nov 1992 09:59:22 GMT

In article <1epg9qINNfb8@OPAL.SYSTEMSX.CS.YALE.EDU>, 
A. Satish Pai <Pai-Satish@CS.Yale.Edu> writes:
|> 
|> Hi, everybody!
|> 
|> Is there any workaround/trick/hack/shell-script that can be used to use find in
|> such a way that it follows symbolic links and descends down them recursively?
|> 
|> I find it annoying that find doesn't follow links. No doubt there are good
|> reasons for making it operate that way but at least there should have been an
|> option to override that, IMHO. Why do I want to follow links? Out here, the
|> "real" directory structure is some hugely complicated thing that only the
|> sysadmins worry about; what users normally see (such as /usr/bin, /homes, etc.)
|> are almost all links to something else. I really don't want to run find with
|> arguments that look like /u6/old/tmp-sys/usr.bin when what I'm thinking of
|> is (say) /usr/bin. Naturally, if I just specify the names I want, find will
|> skip entire directories because something at the top happens to be a sym link.

Under SunOS 4.1.1 the following works:

 eos6c02 tmp 102 > find /bin -name sh -print 
 eos6c02 tmp 103 > find /bin/ -name sh -print
/bin/sh

which sounds like it does at least part of what you want. Otherwise try
perl, it has routines to emulate find that can follow symbolic links if
you want.

-- 

Michael Salmon

#include	<standard.disclaimer>
#include	<witty.saying>
#include	<fancy.pseudo.graphics>

Ericsson Telecom AB
Stockholm
Newsgroups: comp.unix.shell
From: christos@deshaw.com (Christos Zoulas)
Subject: Re: Action of `echo */'
Organization: D. E. Shaw & Co.
Date: Fri, 20 Nov 1992 01:29:38 GMT

In article <1992Nov19.163705.15795@eua.ericsson.se> per@erix.ericsson.se (Per Hedeland) writes:
>In article <1eg04jINN9go@sprocket.csv.warwick.ac.uk>, cudcv@csv.warwick.ac.uk (Rob McMahon) writes:
>|> SunOS 4.1.3, tcsh 6.02.00, bash 1.12.1.
>...
>|> Aagh!  Say what ?  I'm sure this used to work, in sh, csh, and tcsh.
>|> Somewhere along the line it's all gone horribly wrong.
>
>It's a bug, er... fix introduced in SunOS 4.1.3. It's in the release
>manual, section 6.6 "POSIX Bugs Fixed", "Kernel":
>
>1039505 Trailing / in pathname should be ignored.
>
>I actually thought it was an improvement, since now 'rm -r dir<tab>' in
>tcsh didn't fail to remove the directory due to the appended '/', but I
>have since come to see the error of my ways...
>
>I have no idea what POSIX says on the issue, but wouldn't treating
>'directory/' as equivalent to 'directory' (rather than 'directory/.',
>which is the pre-4.1.3 behaviour), while treating 'file/' as
>nonexistent, make everybody happy?
>

The solution is to compile tcsh adding:

#define NAMEI_BUG

in config.h...

I consider the POSIX behavior to be a bug, not a feature!
I agree 100% with Per that trailing slashed should be ignored in directories,
but not in files....

Tcsh-6.03 which will be released *very* soon now will have this as the
default for sunos-4.1.3 and SVR4.

christos
Newsgroups: comp.unix.shell
From: rob@xyzoom.info.com (Rob Lingelbach)
Subject: tcsh problem
Organization: Altruistic Intentions, Hollywood CA
Date: Mon, 16 Nov 1992 06:56:20 GMT

Running version 6.01 of tcsh, I have a strange terminal backspace-key
situation that I wonder if anyone else has observed.  (OS is ISC v3.0,
pretty much plain-vanilla sysv for 386)

If I turn on the correct feature, with a "set correct=all", and then
use the "e" option of the correction prompt to edit a mistyped
command, using a backspace within an interactive script only works
once--a second backspace immediately following the first backspace is
something else (I'm guessing maybe ^D, or eof).  The output of "stty
-a" before and after using the "e" correction option is the same.
Example follows:

rob@xyzoom 22:41 ~ 63> Pnewt
CORRECT>Pnews (y|n|e)?edit
Pnews (I backspaced over the t and typed s, so far so good)
Newsgroup(s): la.tset (now I want to backspace over t, e, and s, to
	correct my bad typing, and as soon as I do the second
	backspace, over the e, I get dumped to the next command of the
	script, the Distribution: prompt).

Backspace works fine at the tcsh prompt--it's only when dealing with
scripts like Pnews that I get the weird behavior.  And I can fix the
behavior each time by doing an "unset correct" (but I like this
feature very much [it's still experimental?]).  If I don't enter the
"e"dit mode of the correction mechanism, and just type "y" to the
tcsh-supplied correction, backspace works fine in scripts.

Thanks in advance for any helpful hints...
--Rob

-- 
Rob Lingelbach KB6CUN | 2660 Hollyridge Dr LA CA 90068 213 464 6266 (voice) 
rob@xyzoom.info.com   | "I care not much for a man's religion whose dog or 
robl@netcom.com       |  cat are not the better for it."  --Abraham Lincoln
Newsgroups: comp.unix.shell
From: ejh@khonshu.colorado.edu (Edward J. Hartnett)
Subject: real easy shell question - PLEASE HELP!!!
Organization: CIRES, University of Colorado
Date: 17 Nov 92 08:27:29

Hi, I'm trying to install gcc 2.3.1 on a Sun IPC running sunos 4.1.1 
I posted this question to gnu.gcc.help and didn't get a single reply.
Could someone please reply, because I've posted about 15 times in the
last two weeks for various problems and haven't gotten a single
answer. It's pretty weird! So if you are outside of colorado, please
reply.

I was trying to redirect the output of my stage three make, but it
printed some messages to stderr and I missed them. Now when I run the
stage three it gives me the following:

[khonshu:/usr/local/gcc/gcc-2.3.1 ! ]# make CC="stage2/xgcc -Bstage2/" CFLAGS="
-g -O" LANGUAGES=c
if [ -f libgcc2.ready ] ; then \
        true; \
else \
        touch libgcc2.ready; \
fi
[khonshu:/usr/local/gcc/gcc-2.3.1 ! ]#

What can I do to run the stage 3 compile without starting all over
again with the tar file? If I delete libgcc3.ready, will that do the
trick? (As you can probably tell, I don't know much about shell
scripts). 

Also in the distribution directory I just found a script dostage3:

#!/bin/sh
make -k LANGUAGES=c $1 CC=stage2/xgcc XCFLAGS=-Bstage2/ CFLAGS="-g $2" >log3 2>&1

Sould I be using this? If I run it with no arguments will it do what I
want? 

Thanks,
	Ed
--
Edward Hartnett			ejh@khonshu.colorado.edu

Newsgroups: comp.unix.shell
From: pershing@teal.csn.org (Paul Pershing)
Subject: Re: Recursive Tree Copy (with filter)?
Organization: Colorado SuperNet, Inc.
Date: Sat, 21 Nov 1992 19:06:39 GMT

Speaking of "recursive."

In zsh 2.1, after defining several functions and aliases that are provided
with the sources, I had three processes suspended and couldn't kill them.
each time I issued a command, either,

kill %1
kill %2
Kill -9 %1
and so on,

I got this error message:

"zsh: job table full or recursion limit exceeded"

The only time I'd seen that message before is when I tried to use
a tcsh alias for safe remove in my zsh, i.e.,

alias rm='rm -i'

with this alias defined in zsh, you get the same error as above.

Anyone know what's going on ?
Thanks in advance,

Paul Pershing

-- 
----------------------------------------------------------------------------
Paul Pershing                          {Clever quote or cliche coming soon!}
Editorial Design/Systems
RMN/400 W. Colfax Ave. Denver, CO 80204 303 892-2633 wk.; 303 233-9231 hm.
From: gwc@root.co.uk (Geoff Clare)
Newsgroups: comp.unix.shell
Subject: Re: Action of `echo */'
Date: 20 Nov 92 18:07:25 GMT
Organization: UniSoft Ltd., London, England

per@erix.ericsson.se (Per Hedeland) writes:

>In article <1eg04jINN9go@sprocket.csv.warwick.ac.uk>, cudcv@csv.warwick.ac.uk (Rob McMahon) writes:
>|> SunOS 4.1.3, tcsh 6.02.00, bash 1.12.1.
>...
>|> Aagh!  Say what ?  I'm sure this used to work, in sh, csh, and tcsh.
>|> Somewhere along the line it's all gone horribly wrong.

>It's a bug, er... fix introduced in SunOS 4.1.3. It's in the release
>manual, section 6.6 "POSIX Bugs Fixed", "Kernel":

>1039505 Trailing / in pathname should be ignored.

This is a kernel bug fix, presumably relating to treatment of pathnames
passed as arguments to system calls.  It has nothing to do with the shell.

>I have no idea what POSIX says on the issue, but wouldn't treating
>'directory/' as equivalent to 'directory' (rather than 'directory/.',
>which is the pre-4.1.3 behaviour), while treating 'file/' as
>nonexistent, make everybody happy?

I don't think POSIX.2 is clear about what `echo */` should expand to.  I
don't have a copy of POSIX.2, but I do have one of XPG4 which is a
superset of POSIX.2.  All I can find on this subject is the following:

    From XCU4 section 2.13.2:

	The asterisk (*) is a pattern that will match any string,
	including the null string.

    From XCU4 section 2.13.3:

	The slash character in a pathname must be explicitly matched by
	using one or more slashes in the pattern; it cannot be matched by
	the asterisk or question-mark special characters or by a bracket
	expression.

It might be interesting to submit this issue to the IEEE for an official
POSIX.2 interpretation.  Any volunteers?
-- 
Geoff Clare <gwc@root.co.uk> (USA antiquated mailers: ...!uunet!root.co.uk!gwc)
UniSoft Limited, London, England.   Tel: +44 71 729 3773   Fax: +44 71 729 3273
Newsgroups: comp.unix.shell
From: per@erix.ericsson.se (Per Hedeland)
Subject: Re: Action of `echo */'
Nntp-Posting-User: per
Organization: Ellemtel Telecom Systems Labs, Stockholm, Sweden
Date: Thu, 19 Nov 1992 16:37:05 GMT

In article <1eg04jINN9go@sprocket.csv.warwick.ac.uk>, cudcv@csv.warwick.ac.uk (Rob McMahon) writes:
|> SunOS 4.1.3, tcsh 6.02.00, bash 1.12.1.
...
|> Aagh!  Say what ?  I'm sure this used to work, in sh, csh, and tcsh.
|> Somewhere along the line it's all gone horribly wrong.

It's a bug, er... fix introduced in SunOS 4.1.3. It's in the release
manual, section 6.6 "POSIX Bugs Fixed", "Kernel":

1039505 Trailing / in pathname should be ignored.

I actually thought it was an improvement, since now 'rm -r dir<tab>' in
tcsh didn't fail to remove the directory due to the appended '/', but I
have since come to see the error of my ways...

I have no idea what POSIX says on the issue, but wouldn't treating
'directory/' as equivalent to 'directory' (rather than 'directory/.',
which is the pre-4.1.3 behaviour), while treating 'file/' as
nonexistent, make everybody happy?

POSIX is your friend...:-)

--Per Hedeland
per@erix.ericsson.se  or
per%erix.ericsson.se@sunic.sunet.se  or
...uunet!erix.ericsson.se!per
From: dansmith@Autodesk.COM (Daniel Smith)
Newsgroups: comp.unix.shell
Subject: Re: echo question
Date: 16 Nov 92 21:55:56 GMT
Organization: Autodesk Inc., Sausalito CA, USA

In <19921114163004SEB1525@MVS.draper.com> SEB1525@MVS.draper.com (Steve Bacher) writes:

> In article <17898@autodesk.COM>,
> dansmith@Autodesk.COM (Daniel Smith) writes:

> >        Forget the escape sequences.  They're not as portable as
> >combining echo with tr:
> >
> >        echo 'first:this=that=other+second:this=that=other+' | tr '=+' '\011\012'

> Hardcoded octal ascii is "portable"???
> Escaping syntax in tr is "portable"???


	Yeah ...

	OK, name an english-language version of Unix this'll bomb on.
When I say "not as portable", I mean that my approach doesn't suffer
portability problems as much as \t \r etc in Sys V echo.

	I'd probably write it in perl though, but that wasn't the question :-)

				Daniel
-- 
     Daniel Smith, Autodesk, Sausalito, California, (415) 332-2344 x 2580
	      Disclaimer: written by a highly caffeinated mammal
	    dansmith@autodesk.com            dansmith@well.sf.ca.us

Newsgroups: comp.unix.shell
From: ejh@khonshu.colorado.edu (Edward J. Hartnett)
Subject: real easy shell question - PLEASE HELP!!!
Organization: CIRES, University of Colorado
Date: 17 Nov 92 17:40:36


Hi, I'm trying to install gcc 2.3.1 on a Sun IPC running sunos 4.1.1 
I posted this question to gnu.gcc.help and didn't get a single reply.
Could someone please reply, because I've posted about 15 times in the
last two weeks for various problems and haven't gotten a single
answer. It's pretty weird! So if you are outside of colorado, please
reply.

I was trying to redirect the output of my stage three make, but it
printed some messages to stderr and I missed them. Now when I run the
stage three it gives me the following:

[khonshu:/usr/local/gcc/gcc-2.3.1 ! ]# make CC="stage2/xgcc -Bstage2/" CFLAGS="
-g -O" LANGUAGES=c
if [ -f libgcc2.ready ] ; then \
        true; \
else \
        touch libgcc2.ready; \
fi
[khonshu:/usr/local/gcc/gcc-2.3.1 ! ]#

What can I do to run the stage 3 compile without starting all over
again with the tar file? If I delete libgcc3.ready, will that do the
trick? (As you can probably tell, I don't know much about shell
scripts). 

Also in the distribution directory I just found a script dostage3:

#!/bin/sh
make -k LANGUAGES=c $1 CC=stage2/xgcc XCFLAGS=-Bstage2/ CFLAGS="-g $2" >log3 2>&1

Sould I be using this? If I run it with no arguments will it do what I
want? 

Thanks,
	Ed
--
Edward Hartnett			ejh@khonshu.colorado.edu
From: moon@Virginia.EDU (Munho Yi)
Newsgroups: comp.unix.shell
Subject: screen(1) and emacs binding
Date: 15 Nov 92 16:19:17 GMT
Distribution: usa
Organization: The University of Virginia

hi,

i am unfortunately not 'emacs' user.
i like to use ctrl-a binding which
move the cursor to the beginning of 
the line.  but in screen session,
all my commands start with ctrl-a
so it seems like i can't use both
at same time.  since i am not familiar
with emacs, i am asking this question
to this group.  please reply to me
by e-mail (moon@virginia.edu) and
i will summerize it later.  thanks.
a