First you will need the ldap search utility. The client for ldap search comes in openldap-clients, so you need to install that first:
sudo yum install openldap-clients
Now, that you have installed it, try to find something in some open ldap server, example:
ldapsearch -LLL -h db.debian.org -x -b "dc=debian,dc=org" "cn=Joao*"
This should list couple of entries for you. Now, that you have ldapsearch working, lets define a function in .bashrc file:
Continue readingTo use this, you will need the lynx tool, so install that first.
sudo yum install lynx
Now, to get list of all the URLs in local html file or some URL, just execute this:
lynx -dump -listonly
Continue reading
Whenever I am writing a script in perl or bash, I always wish that there
was some way to have all the commands logged or output to screen. I know
there is “set -x” option to have debugging enabled, but sometimes that
seems to be too much information and I dont really need all that. So, here
is something I found recently for bash to log all the executed commands.
Just copy this script to your web-server cgi-bin directory and enjoy.
The script with show the common errors like 404 Error, Internal Server Error and others. It will show the User agent distribution using simple commands like grep, uniq, awk and so on.
You would need to change the tfile – which is temporary file and also the access.log path in the next line.
Just re-direct the output to some file with html extenstion. You could even put this in the cron which re-directs the output to some html in server document root.
Continue reading
You can first set the bash mode to vi. This will enable some vim like features to bash. So, add this to .bashrc :
set -o vi
Once, you have done that then its time to get more out of the vi mode. First, check some things and set some interesting stuff.
Continue readingHere is a link of a useful 10K lines bashrc
You may not want to put the whole thing, but get an idea and use what you think can be helpful to you or at-least get an idea. This was not posted by me, so if you are re-using code as is, check the permissions to copy.
Here is script that checks all the colorschemes in the current directory and corrects them if possible (Processing of the file is done with simple commands like sed, grep)
Checks that the color_name is same as Filename
Here is the script:
#!/bin/bash -
#===============================================================================
#
# FILE: check_colors.sh
#
# USAGE: ./check_colors.sh
#
# DESCRIPTION:
#
# OPTIONS: ---
# REQUIREMENTS: ---
# BUGS: ---
# NOTES: ---
# AUTHOR: Amit Agarwal (aka),
# REVISION: ---
#===============================================================================
cd ~/.vim/colors
for i in *vim
do
#echo "Processing $i"
if [[ $(grep -c g:colors_name $i ) -eq 0 ]]; then
if [[ $(grep -c colors_name $i ) -eq 0 ]]; then
echo "File $i does not have colorname";
missing=$missing" $i"
else
sed -i.bak '/colors_name/ s/.*/let g:colors_name="'${i//.vim}'"/g' $i
fi
else
if [[ $(grep -c colors_name $i|grep let ) -gt 1 ]]; then
echo "WARN ----->> File $i has more than one colorsname"
fi
colorname=$(grep g:colors_name $i|grep let| sed -e 's/"//g' -e 's/.*=//' |tr -d ' ')
if [[ ${colorname}.vim != $i ]]; then
echo "Filename $i does not match colorname $colorname .. correcting "
sed -i.bak '/colors_name/ s/.*/let g:colors_name="'${i//.vim}'"/g' $i
#sed -i.bak 's/(.*g:colors_name.*=)/1'${i//.vim}'/g' $i
fi
fi
done
if [[ x$missing != x ]] ; then
echo "Missing colornames in $missing"
fi
Continue reading
