HP 382 - Page 61

FINAL TRIM SIZE : 7.5 in x 9.0 in
4
A
.rhosts
le
in
the
remote
host
home
directory
con
taining
the
names
of
y
our
lo
cal
host
system
and
your
lo cal
login name.
A .rhosts
le on
your
lo
cal
system,
as
w
ell.
This
con
tains
the
names
of
all
the
systems
y
ou
will
cop
y
from.
It
will
ensure
that
y
ou
will b
eable
to use
rcp
when
y
ou
use
rlogin on
the remote
system.
Note
A
$HOME/.rhosts
le
creates
a signican
t securit
y risk.
To
prev
ent
unauthorized
users
form
gaining
remsh
access
to
y
our
remote
accoun
t
and
host,
only
you
should
b
e
able
to
create
and
write
to
a
.rhosts
le
in
y
our
remote
home
directory.
P
ermissions
need to
b
e
set
accordingly
.
A
/etc/host
le
on
y
our
lo
cal
system
whic
h
lists
hosts
with
which
you
can
communicate
using
ARP
A/Berk
eley
Services.
F
or
eac
h
host,
the
le
has
a
line
con
taining
information
ab
out the
remote host
in
the
follo
wing
form:
internet addr
ess
ocial
name
alias
Y
ou
will
nd that
the
/etc/hosts
le
is
useful
for
lo
oking
up
names
and
addresses
on
the
net
w
ork.
T
o
facilitate
suc
ha
lo
okup,
use
the
grep
to
ol
describ
ed
in
gr
ep
(1)
and
in
Using
HP-UX
.
Cop
ying
a
Local
File
to
a Remote
Host
T
o
cop
y
from y
our system
to a
remote
system,
use
the
follo
wing
syn
tax:
rcp lo
c
al
lename r
emote
hostname :
r
emote
lename
Note
that,
if
lo
c
al
le
is
not
in
y
our
curren
t
directory
,
y
ou
will
need
to
supply
the
relative
path (to
get from
y
our
curren
t
directory)
or
the
absolute
path
(from
/
),
in
addition to
the lo
cal le
name. Y
ou will
need to
specify
the
complete
(absolute)
path
for
the
r
emote
lename
on
r
emote
hostname
only
if
you w
antit togo in
to a directory other than
the remote home directory
.
For example, to cop
y myfile from y
our curren
t directory to a remote system
called
xyz :
rcp myfile xyz:/users/leslie/otherdir
Using the Command Line 4-21