Date: Tue, 28 Oct 2003 14:01:53 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: nw1 <network101@covad.net> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD-4.8 -- Strange behavior using dump(8) -- Message-ID: <20031028140153.GA9271@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <002b01c39d4c$ccecc450$0300a8c0@install> References: <002b01c39d4c$ccecc450$0300a8c0@install>
next in thread | previous in thread | raw e-mail | index | archive | help
--PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 28, 2003 at 07:12:46AM -0500, nw1 wrote: > This problem can be viewed @ http://69.3.136.141/freebsd/dump8/dump8_issu= e-1 Hmmm... I don't see why you couldn't just send that to the list. In summary, you're trying to run dump(8) to a remote file, and it's just hanging: dump 0af user@box1.domain.net:testfile / DUMP: <-- We receive that as a result --and it just sits there. =20 This smells to me that the rcmd(3)/rshd(8) facility that remote dumping uses hasn't been enabled. Let me say two things about this: i) One way of making this work is to enable rshd(8) by uncommenting the appropriate line(s) in /etc/inetd.conf on box1.domain.net -- ie: shell stream tcp nowait root /usr/libexec/rshd rshd shell stream tcp6 nowait root /usr/libexec/rshd rshd Then you will need to set up /etc/hosts.equiv and/or .rhosts (see hosts.equiv(5)) in order to permit passwordless access to box1.domain.com from the machine you want to backup. Then your remote dump should proceed as desired. However, preferably, don't do this but use the following instead. ii) Although the man page for rcmd(3) or rcmdsh(3) don't mention it, you can actually substitute for rsh(1) by setting the RSH environment variable to the name of the alternate command. See: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D15830 or look at /usr/src/lib/libc/net/rcmd.c around line 113. I've ranted elsewhere in this mailing list about the general desirability of secure protocols like SSH and their superiority over rsh quite recently, so I'll spare you a repeat of that. Suffice it to say that instead of (i) above I would most strongly suggest that you: # setenv RSH /usr/bin/ssh # dump 0af ... and you should read the ssh FAQ entry about unattended login at: http://www.snailbook.com/faq/no-passphrase.auto.html and also make maximum use of the facilities of the ~/.ssh/authorized_keys file as described in the section "AUTHORIZED_KEYS FILE FORMAT" in the sshd(8) man page -- particularly 'from=3D"..."', 'command=3D"..."', 'no-port-forwarding' and 'no-X11-forwarding', 'no-agent-forwarding'. [The command you'll be running in this remote dump case is /usr/sbin/rmt] Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/nnbRdtESqEQa7a0RAs8XAJkBvcilpLD7Fj8STcmhhNAT06erdwCgkgrs 3lbApWzg7P1FHOTQEVamOK8= =4BE6 -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031028140153.GA9271>