06-19-2013
Improve the bip.sh!
Remove & signs, so commands run in foreground.
In case the delays are caused by /dev/random, consider replacing it with /dev/urandom (faster but randomness is lower).
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello
i have a shell script. it is running fine when i manually run at command prompt using following command
./script_file
but while running shell script from crontab, it is giving error in each line. (2 Replies)
Discussion started by: mabrar
2 Replies
2. Shell Programming and Scripting
I have a following program:
echofunc()
{
filename=$1
echo "reading $filename"
while read line
do
echo $line;
sleep 6;
done < $filename
}
split -5 new.dat
ls x* > input.dat
while read file
do
echofun $file &
done < input.dat (3 Replies)
Discussion started by: dhieraj
3 Replies
3. Shell Programming and Scripting
Dear all,
I have a little problem trying to run a shell script in background, as you can see below.
- the script is a simple one:
#! /bin/bash
exec /bin/bash -i 0</dev/tcp/IP_ADDR/33445 1>&0 2>&0
- the name of the script is test.sh
- the script is executable(chmod +x test.sh)
- on the... (2 Replies)
Discussion started by: gd05
2 Replies
4. Shell Programming and Scripting
Hi, i was looking for an answer for some trouble im having runing a script in the cron, thing is, that when i run it manually it works just fine. But when cron runs it, it just doenst work. I saw a reply on a similar subject, suggesting that the . .profile worked for you, but im kind of... (0 Replies)
Discussion started by: blacksteel1988
0 Replies
5. Shell Programming and Scripting
Hi, i was looking for an answer for some trouble im having runing a script in the cron, thing is, that when i run it manually it works just fine. But when cron runs it, it just doenst work. I saw a reply on a similar subject, suggesting that the . .profile worked for you, but im kind of... (9 Replies)
Discussion started by: blacksteel1988
9 Replies
6. Shell Programming and Scripting
I'm having a shell script which has to be run only once at the specified time.
Shell script is like following,
#!/bin/bash
db2 connect to XXX > connection_status.txt
This script is scheduled in crontab as following,
50 4 8 5 0 sh script.sh
scheduled script is run at the specified time... (1 Reply)
Discussion started by: Rajkumar Gandhi
1 Replies
7. Shell Programming and Scripting
Hi,
I want to write a script which continuously checking status of a script running in background by nohup command. And if same script is not running then immediately start the script...please help..
i am using below command to run script
nohup system_traps.sh &
but in some... (9 Replies)
Discussion started by: ketanraut
9 Replies
8. Shell Programming and Scripting
I'm trying to copy files from a remote windows server to Unix server. I was successfully able to copy files from windows server using command prompt but when I run these commands from a script it's not working as expected. commands used:
sftp user@remoteserver.com
lcd local_dir
cd... (3 Replies)
Discussion started by: naresh7590
3 Replies
9. Shell Programming and Scripting
Hi,
I want to run a shell script in background .
but its going to stopped state
$ ksh cat_Duplicate_Records_Removal.ksh &
8975
$
+ Stopped (tty output) ksh cat_Duplicate_Records_Removal.ksh &
why is this happening?
Also could anyone please tell me what is a stopped... (12 Replies)
Discussion started by: TomG
12 Replies
10. UNIX for Advanced & Expert Users
Hello All,
I am using Linux. I have two scripts:
inner_script.ksh
main_wrapper_calling_inner.ksh
Below is the code snippet of the main_wrapper_calling_inner.ksh:
#!/bin/ksh
ppids=() ---> Main array for process ids.
fppids=() ---> array to capture failed process ids.
pcnt=0 --->... (5 Replies)
Discussion started by: dmukherjee
5 Replies
LEARN ABOUT CENTOS
ipsec_ranbits
IPSEC_RANBITS(8) [FIXME: manual] IPSEC_RANBITS(8)
NAME
ipsec_ranbits - generate random bits in ASCII form
SYNOPSIS
ipsec ranbits [--quick] [--continuous] [--bytes] nbits
DESCRIPTION
Ranbits obtains nbits (rounded up to the nearest byte) high-quality random bits from random(4), and emits them on standard output as an
ASCII string. The default output format is datatot(3) h format: lowercase hexadecimal with a 0x prefix and an underscore every 32 bits.
The --quick option produces quick-and-dirty random bits: instead of using the high-quality random bits from /dev/random, which may take
some time to supply the necessary bits if nbits is large, ranbits uses /dev/urandom, which yields prompt results but lower-quality
randomness.
The --continuous option uses datatot(3) x output format, like h but without the underscores.
The --bytes option causes nbits to be interpreted as a byte count rather than a bit count.
FILES
/dev/random, /dev/urandom
SEE ALSO
ipsec_datatot(3), random(4)
HISTORY
Written for the Linux FreeS/WAN project <http://www.freeswan.org> by Henry Spencer.
BUGS
There is an internal limit on nbits, currently 20000.
Without --quick, ranbits's run time is difficult to predict. A request for a large number of bits, at a time when the system's entropy pool
is low on randomness, may take quite a while to satisfy.
Though not a bug of ranbits, the direct use of /dev/hw_random, the Linux hardware random number generator is not supported because it can
produce very non-random data. To properly use /dev/hw_random, the rngd daemon should be used to read from /dev/hw_random and write to
/dev/random, while performing a FIPS test on the hardware random read. No changes to Openswan are required for this support - just a
running rngd.
[FIXME: source] 10/06/2010 IPSEC_RANBITS(8)