Re: PRNGD is not seeded
- From: "N. Yaakov Ziskind" <awacs@xxxxxxxxxx>
- Date: Tue, 24 Mar 2009 00:01:05 -0400
brian@xxxxxxxxx wrote (on Fri, Mar 13, 2009 at 05:46:32PM -0700):
On Mar 12, 9:09 pm, "N. Yaakov Ziskind" <aw...@xxxxxxxxxx> wrote:
i'm getting the message that PRNGD is not seeded when running ssh onrsync does not require ssh.
a 5.0.5 box. The ssh is some version:
OpenSSH_3.7.1p2, SSH protocols 1.5/2.0, OpenSSL 0.9.7d 17 Mar 2004
that I got from a tarball somewhere. Prngd was installed via custom
from prngd-0.9.23-VOLS.tar that I got from somewhere else. Prngd starts
nicely:
prngd 1426 1 0 20:55:18 ? 00:00:00 /usr/local/sbin/prngd /usr/
local/var/prngd/prngd-pool
All the relevant files exist in the proper paths, I think, as delineated
in /etc/init.d/prngd. No information in /usr/local/var/prngd/prngd.log;
in fact, running prngd from the command line succeeds silently. Running it
with the -d flag yields nothing of interest:
[...]
Spawned gatherer (pid = 1789): /usr/bin/sar (sar)
Caught SIGCHLD (pid = 1789, gatherer_pid = 1789)
Read 1652 bytes from gatherer
Read 0 bytes from gatherer
Closing connection to gatherer
[...]
I'm stumped here. I'm wondering if I should install OSS646, but the box
is shaky (and miles away, with a flakey tape drive ...) and I'd really
like to install rsync, which requires ssh (right?) which requires prngd
...
ssh without any arguments displays its usage message, suggesting that I
installed it (somewhat) correctly. The tar ball had (certain) library
files on it, which I installed.
Any suggestions? Is it possible that prngd is operating properly, but
ssh is not talking to it? How would I test that?
Thanks ...
you need to find some pretty old binary for rsync somewhere if you
can't
install oss646c.
Though, if your need is great you can extract just the couple needed
libs from oss646c or from any 507 box (or updated 506 box) and use
LD_LIBRARY_PATH to run rsync and force it to load these other libs
from
a separate directory without installing them over top of the stock
ones.
Without looking, I believe The needed libs are just libc and
libsocket.
Use ldd /path/to/rsync to find out for sure.
Current versions of rsync have a several advantages over old ones,
The biggest one to me is it no longer needs to assemble the full file
listing for the entire job up front, instead now it starts working on
a
chunk of files and proceeds to work on more chunks until the job is
done, meaning you no longer have to worry about breaking large jobs
into
smaller ones, you can do whole filesystems in one command.
Another is -z automatically skips several common already-compressed
file
formats so, you can just leave -z in all your commands and it will not
waste cpu and time trying to compress jpegs and tar.Z's.
With the LD_LIBRARY_PATH trick you may be able to use the version 3.0
binary I have here:
http://www.aljex.com/bkw/#rsync
I just discovered a few days ago that this binary fails to run on
5.0.5
even with oss646c installed. However, the 2.5.6 binary from the same
place does run.
There are even older binaries around elsewhere that were built on old
systems even before 5.0.4.
I have somehow lost the means to compile stuff. when I follow my own
recipe that I've used for years for setting up a new osr5 system and
build environment, but with the most recent versions of the packages
(osr507, linker&libs, osr507mp5, gnutools507Kj), something somewhere
isn't right. So, I have no rsync 3.0.5 to offer.
As for ssh, I believe that as of that 2.5.6 binary I was still
configuring the compile-time default for the -e option to use rcmd
instead of ssh, because back then most of the sco boxes I touched
still
had no ssh but rcmd was always installed and enabled by default. So,
that particular binary wouldn't even try to use ssh by default. But
regardless of the default, you can always use -e rcmd to override the
default. If the server is linux then on the server you have to install
and enable rsh-server on linux which is usually not installed by
default
any more. Or better yet, you can use native rsync instead of either
rsh
or ssh. I do this last simply for speed.
-- bkw
Thanks to everyone who replied, especially to this poster, who
pointed me in the right direction.
I threw the dice and installed OSS646, and the box didn't keel
over, but it did kill whatever ssh I installed: "you don't exist,
go away!" which I'm given to understand that I have the 'wrong' ssh
(i.e., compiled w/o reference to OSS646.) So, I gave up on ssh.
I finally set up a rsync server on the nearest linux box, and rsync
happily ran like a champ. And The Data Was Saved.
And now, of course, the Unix box that was dying - not booting
and so forth - is happily running, and sneering at the windows
workstations. But I imagine you knew that.
I *would* like to know more about how ssh fails to grasp PRNGD, but
not enough, I suppose, to either a) rip out OSS646; or b) import
a new ssh. So, I'll leave it for now.
--
_________________________________________
Nachman Yaakov Ziskind, FSPA, LLM awacs@xxxxxxxxxx
Attorney and Counselor-at-Law http://ziskind.us
Economic Group Pension Services http://egps.com
Actuaries and Employee Benefit Consultants
.
- References:
- PRNGD is not seeded
- From: N. Yaakov Ziskind
- Re: PRNGD is not seeded
- From: brian@xxxxxxxxx
- PRNGD is not seeded
- Prev by Date: Re: PRNGD is not seeded
- Next by Date: Re: Samba 3.0.14Aa on 506
- Previous by thread: Re: PRNGD is not seeded
- Next by thread: Xenix
- Index(es):
Relevant Pages
|
Loading
