Skip to main content

Linux Live Search...

So... The other day I decided to set up 'locate' to find files in my home network shares, /home/ghostis and /sandbox/ghostis. To do so, I did the following:


% mkdir /home/ghostis/Documents/locate

Added the an updatedb job to my crontab on my laptop:

15,30 * * * * updatedb --netpaths='/home/ghostis /sandbox/ghostis' --output=/home/ghostis/Documents/locate/locatedb --localpaths=' '

Now I can do faster searches of filenames via:

locate -d ~/Documents/locate/locatedb sometextinfilename


But, then I thought, "What's the absurd extreme?"
Linux Live Search!
So I baked a quick bash script:

% cat linux_live_search.sh


#!/bin/bash
clear
echo "Please type something. (Escape spaces. Ctrl-C to quit)"
echo "------------------------------------------"
echo "Query: $WORD"
echo "------------------------------------------"
while read -s -n1 KEY
do
  clear
  if [ "$KEY" = "" ]
  then
    WORD=`echo "$WORD"| sed -e 's/.$//'`
  else
    WORD="`echo "$WORD"`$KEY"
  fi
  if [ "$KEY" = "" ]
  then
    unset WORD
  fi
  if [ -z "$WORD" ]
  then
    echo "Please type something. (Escape spaces. Ctrl-C to quit)"
  else
    killall locate > /dev/null 2>&1
    locate --all -d ~/Documents/locate/locatedb "$WORD" | head -30
  fi
  echo ""
  echo "------------------------------------------"
  echo "Query: " "$WORD"
  echo "------------------------------------------"
done




Try not to choke on your coffee...

Cheers,

-Adam
Labels:

Comments

Post a Comment

Popular posts from this blog

Fixing SSH connection problems in EGit in Eclipse

Note: I posted a version of this on Stack Overflow. Errors can occur when there is an underlying SSH authentication issue, like having the wrong public key on the git remote server or if the git remote server changed its SSH host key. Often the an SSH error will appear as: " Invalid remote: origin: Invalid remote: origin" Eclipse will use the .ssh directory you specify in Preferences -> General -> Network Connections -> SSH2 for its ssh configuration. Set it "{your default user directory}.ssh\" . To fix things, first you need to determine which ssh client you are using for Git. This is stored in the GIT_SSH environmental variable. Right-click on "Computer" (Windows 7), then choose Properties -> Advanced System Settings -> Environment Variables. If GIT_SSH contains a path to plink.exe, you are using the PuTTY stack. To get your public key, open PuTTYgen.exe and then load your private key file (*.ppk). The listed public key sho
Post a Comment
Read more

PowerShell One-Liners

Introduction PowerShell is Microsoft's shell for their product lines. It's now on version 3.0. If you miss the power of the command line while using Windows on either your laptop or servers, PowerShell provides that power. Important concepts: Almost all aspects of the Microsoft ecosystem are objects within an overarching structure. You query and manipulate this structure and its objects with PowerShell. This includes all aspects of SharePoint, Active Directory, and Exchange. Other companies, like VMware (see below) have also written PowerShell modules. This "object nature" means that PowerShell pipes pass objects and properties, not just text.  Variables store data-structures of objects.  One-liners Note: Unwrap the code lines before you use them. Get Help Get the usage of the command "Select-Object": Get-Help Select-Object Built-in examples for the command "Select-Object": Get-Help Select-Object -exam
Post a Comment
Read more

How to fix this ssh error from a Cisco switch: ssh_rsa_verify: RSA modulus too small: 512 < minimum 768 bits

Problem ssh user@cisco_switch returns: ssh_rsa_verify: RSA modulus too small: 512 < minimum 768 bits key_verify failed for server_host_key Solution The modulus of the ssh RSA key pair on the switch is too small. If you have access, generate a new key pair on the switch with a larger modulus. Procedure Login with ssh protocol version 1 ( ssh space dash one ): ssh -1 user@cisco_switch (On the switch): enable (On the switch): Authenticate to "Privileged Exec Mode" mode on the switch. (On the switch): conf t (On the switch): crypto key generate rsa general-keys modulus 1024 (On the switch): Press enter to accept that the current key pair for the switch will be replaced. You now should be able to log into the switch with ssh protocol version 2.
Post a Comment
Read more