HP3000-L Archives

November 1997, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Stigers, Greg ~ AND" <[log in to unmask]>
Reply To:
Stigers, Greg ~ AND
Date:
Mon, 10 Nov 1997 16:26:52 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (57 lines)
Absolutely!

If you wish, and are more comfortable with a UNIX convention, you can
have a .netrc (it must be lowercase) in the homegroup or the working
directory of the user running the ftp. What I am used to for netrc under
MPE is to have just as many entries as you need in the form:
machine machinename login username password userpassword
where machine, login, and password are tokens that must be lowercase,
and machinename, username, userpassword are the appropriate values
(machinename being an entry in your HOSTS.NET.SYS file). Secure the
devil out of this file. Consider putting in another account, and
granting access only to the ftp user, and the system manager. To use the
file, you must set a file equation in the form
FILE NETRC.HOMEGROUP=FILE.GROUP.ACCOUNT
So you can name the file anything you want, and put it anywhere you
want, so long as the ftp user(s) can read the file. I use a special ftp
user that only runs in batch, and set this file equation in a secured
logon UDC. Then, you can issue a
RUN FTP.ARPA.SYS;INFO="FTPHOST";STDIN=FTPFILE.CMDFILE
where FTPHOST is the machine name in your netrc file, and
FTPFILE.CMDFILE contains just the ftp commands after the login, in your
example, starting with macdef init. I have used job streams for this
that consisted of the JOB statement, the RUN FTP statement, and !EOJ.
Works great. Reply with any questions.

>----------
>From:  Douglas Caviness[SMTP:[log in to unmask]]
>Sent:  Friday, November 07, 1997 6:03 PM
>To:    [log in to unmask]
>Subject:       [HP3000-L] FTP under MPE/iX
>
>On UNIX machines, if you create a file called .netrc in your home directory,
>and set the permissions on the file correctly, you can automate file
>transfers. For instance, if .netrc contains:
>
>machine oboe
>login frank
>password frankpassword
>macdef init
>asc
>get asciifile
>quit
>
>If user frank issues the command "ftp oboe", he will automatically be
>connected to oboe, logged on, the ascii transfer mode turned on, the file on
>the remote machine "asciifile" will be transferred to the local machine, and
>then ftp will be terminated.
>
>QUESTION: does ftp under MPE/iX have the same capability? What would the name
>be for the .netrc file, and where would it be located? Logging in as
>MANAGER.SYS, and automaticaly being put into the group PUB.SYS, I created
>netrc, .NETRC and NETRC, with no joy. Any suggestions?
>
>Douglas Caviness - TTC Systems Support
>[log in to unmask]
>

ATOM RSS1 RSS2