Hi there,
I try to use:
> find * | ls
but it just gave me one level of ' ls '. and it said:
> find * | ls
dir1 dir2 f1 f2 f3
Broken Pipe
>
what is broken pipe?
how can i fix it?
thks
Gusla (3 Replies)
sometimes I ftp files from an Unix environment from the command prompt of my win2000 pc and I get a "broken pipe" message. sometimes I'll get nothing but sometimes I'll get part of the file.
Whats this "broken pipe" about?? (3 Replies)
Hi
I tried to open the man page of sh and piped to `pg`. Normally while reading a file page by page using `pg`, if we wanna quit at the middle of file, we give "q" near the colon mode.
Ex1: $cat file1 | pg
hi
how
r
u
: (page1) now press "return key", it will go to next page
yes
i ... (1 Reply)
Hi
I tried to open the man page of sh and piped to `pg`. Normally while reading a file page by page using `pg`, if we wanna quit at the middle of file, we give "q" near the colon mode.
Ex1: $cat file1 | pg
hi
how
r
u
: (page1) now press "return key", it will go to next page
yes
i ... (3 Replies)
hi
i have a server, and i have a web site and i installed apache in the /usr/local/apache/logs
i have a file and i have this problem
(32)Broken pipe: core_output_filter: writing data to the network
plz help me how i can resolve this
plz it's urgent
th (2 Replies)
hi
i have a server, and i have a web site and i installed apache in the /usr/local/apache/logs
i have a file and i have this problem
(32)Broken pipe: core_output_filter: writing data to the network
plz help me how i can resolve this
plz it's urgent
th (1 Reply)
hi
i am trying to upload a file using ftp protocol,
i am facing some problem while uploading
"Failedtoupload:SFTREGUP1:FTP_ASCII_MAILBOX21.39.10.856305000:Broken pipe"
Can someone explain why it is coming , and the solution . (0 Replies)
I know what causes 'broken pipe' errors, but I can't understand why I can get it (only occasionally) with my example:
ps -ef | grep "\./ans$" | grep -v grep
Basically I'm searching the ps output looking for the process I'm interested in and excluding the process that is grepping for the... (2 Replies)
I'm new to scripting, and this forum has been invaluable in helping me out. I'm hoping I can get some personal help now though.
I have a korn script that takes a list of servers and either telnets or sshs into it (only some are set up for ssh). What I'm doing now is trying to telnet first, and... (10 Replies)
Discussion started by: aimeet
10 Replies
LEARN ABOUT REDHAT
urandom
RANDOM(4) Linux Programmer's Manual RANDOM(4)NAME
random, urandom - kernel random number source devices
DESCRIPTION
The character special files /dev/random and /dev/urandom (present since Linux 1.3.30) provide an interface to the kernel's random number
generator. File /dev/random has major device number 1 and minor device number 8. File /dev/urandom has major device number 1 and minor
device number 9.
The random number generator gathers environmental noise from device drivers and other sources into an entropy pool. The generator also
keeps an estimate of the number of bit of the noise in the entropy pool. From this entropy pool random numbers are created.
When read, the /dev/random device will only return random bytes within the estimated number of bits of noise in the entropy pool.
/dev/random should be suitable for uses that need very high quality randomness such as one-time pad or key generation. When the entropy
pool is empty, reads to /dev/random will block until additional environmental noise is gathered.
When read, /dev/urandom device will return as many bytes as are requested. As a result, if there is not sufficient entropy in the entropy
pool, the returned values are theoretically vulnerable to a cryptographic attack on the algorithms used by the driver. Knowledge of how to
do this is not available in the current non-classified literature, but it is theoretically possible that such an attack may exist. If this
is a concern in your application, use /dev/random instead.
CONFIGURING
If your system does not have /dev/random and /dev/urandom created already, they can be created with the following commands:
mknod -m 644 /dev/random c 1 8
mknod -m 644 /dev/urandom c 1 9
chown root:root /dev/random /dev/urandom
When a Linux system starts up without much operator interaction, the entropy pool may be in a fairly predictable state. This reduces the
actual amount of noise in the entropy pool below the estimate. In order to counteract this effect, it helps to carry entropy pool informa-
tion across shut-downs and start-ups. To do this, add the following lines to an appropriate script which is run during the Linux system
start-up sequence:
echo "Initializing kernel random number generator..."
# Initialize kernel random number generator with random seed
# from last shut-down (or start-up) to this start-up. Load and
# then save 512 bytes, which is the size of the entropy pool.
if [ -f /var/random-seed ]; then
cat /var/random-seed >/dev/urandom
fi
dd if=/dev/urandom of=/var/random-seed count=1
Also, add the following lines in an appropriate script which is run during the Linux system shutdown:
# Carry a random seed from shut-down to start-up for the random
# number generator. Save 512 bytes, which is the size of the
# random number generator's entropy pool.
echo "Saving random seed..."
dd if=/dev/urandom of=/var/random-seed count=1
FILES
/dev/random
/dev/urandom
AUTHOR
The kernel's random number generator was written by Theodore Ts'o (tytso@athena.mit.edu).
SEE ALSO
mknod (1)
RFC 1750, "Randomness Recommendations for Security"
Linux 1997-08-01 RANDOM(4)