*BSD News Article 18181


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!howland.reston.ans.net!noc.near.net!uunet!haven.umd.edu!umd5.umd.edu!elea.umd.edu!mark
From: mark@elea.umd.edu (Mark Sienkiewicz)
Newsgroups: comp.os.386bsd.questions
Subject: Re: Challenge
Date: 9 Jul 1993 15:33:05 GMT
Organization: University of Maryland
Lines: 25
Message-ID: <21k33h$9r5@umd5.umd.edu>
References: <GSPIEGEL.127.742156302@bsa3.kent.edu>
NNTP-Posting-Host: elea.umd.edu
Keywords: cron

In article <GSPIEGEL.127.742156302@bsa3.kent.edu> GSPIEGEL@bsa3.kent.edu (Greg Spiegelberg) writes:
>Here's my problem
>3)  I'd then like the cron file to automatically ftp to our ftp server 
>    (which happens to get backed up regularly).


You need to use 'ftp -n' to make it _not_ prompt for the user name and 
password.  For example:

ftp -n << ARFARF
open other_computers_name
user some_user_name some_password
put file_you_want_to_send
quit
ARFARF

The weakness here is that you must specify a user name and password in the
script file.  I would recommend that your ftp server have a username/password
pair that is used exclusively for making the backups, and which is not
allowed to log in interactively.  I would not recommend using anonymous
ftp because you don't know if some anonymous user is going to trash your
backup files.

Mark S.