# verify randomness $ t=0; for i in {1..1000000}; do ran 100 && t=$((t+1));done; echo $t 1000000 $ t=0; for i in {1..1000000}; do ran 20 && t=$((t+1));done; echo $t 200174 $ t=0; for i in {1..1000000}; do ran 0 && t=$((t+1));done; echo $t 0 # usage: $ ran 20 && echo 20% hit
Randomly decide whether to run a command, or fail.
It's useful for testing purposes.
.
Usage: ran PERCENTAGE COMMAND [ARGS]
Note: In this version the percentage is required.
.
This is like @sesom42 and @snipertyler's commands but in a USABLE form.
.
e.g. In your complicated shell script, put "ran 99" before a crucial component.
Now, it will fail 1% of the time allowing you to test the failure code-path.
ran 99 my_complex_program arg1 arg2
Show Sample Output
Command will succeed n% of the time. ran 75 will cause command to succeed 75% of the time. No argument will cause it to succeed 50% of the time. Show Sample Output
Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?
You must be signed in to comment.
commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for: