nv-l

Re: responding to prompt in ksh script

1999-02-17 12:21:11
Subject: Re: responding to prompt in ksh script
From: Steve Francis <sfrancis AT COMMSERV.UCSB DOT EDU>
To: nv-l AT lists.tivoli DOT com
Date: Wed, 17 Feb 1999 12:21:11 -0500
The more generic and expandable way to do this is to use expect and tcl.  Of
course, this requires you learn expect, but I find it invaluable in nework
management.

Booker Rosemary wrote:

> I've actually used a single command line prompt in a script for ftp
>
> ftp -v -n wis2 < nms.params
>
> where nms.params =
> user <username> <userpassword>
> ascii
> put <filename>
>
> This way I don't have to wait for prompts from ftp.
>
> I think tftp has the same sort of functionality.
>
> Rosemary
>
> > -----Original Message-----
> > From: Lucy Premus [SMTP:lpremus AT METLIFE DOT COM]
> > Sent: Wednesday, 17 February 1999 6:22
> > To:   NV-L AT UCSBVM.ucsb DOT edu
> > Subject:      responding to prompt in ksh script
> >
> > I want to do a tftp, from a ksh script, to another system to retrieve
> > files that
> > my script is going use.  Is this possible?  How do I know when I get the
> > tftp>
> > prompt so that I could issue my get command and then of course quit from
> > the
> > tftp connection?
> **********************************************************************
> CAUTION: This Message may contain confidential information intended
> only for the use of the addressee named above. If you are not the
> intended recipient of this message you are hereby notified that any
> use, dissemination, distribution or reproduction of this message is
> prohibited. If you received this message in error please notify
> Mail Administrators immediately. Any views expressed in this
> message are those of the individual sender and may not necessarily
> reflect the views of Woolworths Ltd.
> **********************************************************************

<Prev in Thread] Current Thread [Next in Thread>