Questions[sh](server)

I have created a shell script to complete 3 simple tasks (zip a directory, rename the final file and delete the source directory). The script source is below:

#!/bin/bash
if [[ $2 == *"/data/"* ]]
then
    src= $2"/*";
    dest= $1".zip";

    # Just for test
    echo $src;

    # Commented for now
    #zip -r -j $dest $src
    #mv $dest $1
    #rm -rf $2
else
    echo "Invalid arguments";
fi

When I run the script above with these parameters I have with error:

./scriptzip.sh /data/file-new /data/file-old

./scriptzip.sh: line 4: /data/file-old/*: No such file or directory
./scriptzip.sh: line 5: /data/file-new.zip: No such file or directory

How can prevent the shell to test a variable for "directory like" string? There is any way to skip that?

I'm attempting to create an ssh tunnel, spin it off into a background process, and write a pid file which I can later use to kill it. I CAN run ssh with -f, but then I don't have a handle on its PID.

However, when I attempt to run the script below via nohup or setsid, control is never returned to the shell from which I attempt to daemonize the script.

#!/bin/sh                                                 

while getopts ":v" flag; do
    case $flag in
        v|verbose) verbose=1;;
        :) echo "option -$lastflag requires an argument"; exit 1;;
    esac 
    lastflag="$flag"
    shift $((OPTIND - 1)); OPTIND=1
done

ssh  -p '2222'  -nNL '5984:localhost:5984' '[email protected]' &
pid=$!
sleep 2;
ps -p $pid >/dev/null 2>&1 || exit 1
echo $pid > "var/couchdb-tunnel.pid"
wait

Invocation:

nohup script.sh
setsid script.sh

How I do convince ssh (I assume) to let go of the terminal? Is there some other way I can accomplish what I want?

I made a really bad decision on one of my servers.

I deleted /bin/sh. I restarted the server and the server won't run because it needs /bin/sh to start the rc scripts. I can't access single user mode either because sh is needed.

Is there any easy way to reinstall the bourn shell?

I tried copying sh from a live cd, it failed on the ld-elf.so.1 library. So I copied that to /libexec from the livecd to my / partition. It then needs the libedit.so library and I copied that to /libexec but it isn't working this time.

I tried a symlink to /usr/local/bin/bash but that still presents me with "can't find sh" type error. I'm assuming that is because /usr isn't mounted yet because it is done from an rc script.

Any help is greatly appreciated.

After a few days of operation on my new ec2 build, the following happens:

1. I log into SSH, everything is fine, I do my coding
2. I return the next day, and log into SSH
3. I cannot type a lower cased e anymore--I get the error ding when I type it
4. I try to ssh from a different computer, same problem
5. I reboot the server, same problem
6. I open nano or vi and e works fine, just not in bash or sh
7. I terminate the server, create a new one, install from scratch, a few days later it happens again

This is baffling! Where do I even start to troubleshoot?

My Local Machine Setup(s):

• windows XP or 7
• putty (latest) or cygwin/openssh

The EC2 setup

• Amazon Linux (default options)
• node.js
• iptables forwarding port 80 to node on port 8003
• emacs, npm, and openssl-devel

• no other mods

• Here is my /etc/profile

• Here is my /etc/inputrc
• Here is my ~/.bashrc and ~/.bash_profile
• output of env

Output of stty -a while I can't type an e

sh-4.1$ stty -a
speed 38400 baud; rows 30; columns 95; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>;
swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V;
flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts -cdtrdsr
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany
-imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke

In case it helps someone else with a similar issue, I created a script (called sub) to convert upper-cased E to lower-cased, then echo the command back. Then I run it in backticks to get an e on the command line::

#!/bin/sh
echo ${@//E/e}

> `sub Emacs /Etc/profilE`

UPDATES

1. This breaks for all users
2. In bash only (csh works fine)
3. In emacs edit mode only

I've created a chat room to discuss this issue and hone in the solution.

The default shell in FreeBSD is sh and I really can't stand it: autocomplete is very limited, and rehash commands kill me. I feel like a one armed and one legged man...

How can I change the shell globally to zsh or bash - for root and for all current and future users?