OnTheEdge wrote:
> I'm trying to check for a directory and create it if it doesn't exist as
> follows:
>
> CommonDir="../common"
> if [ -d ${CommonDir} ]; then
>mkdir "${CommonDir}"
> fi
>
> It works from the command line, but my script doesn't seem to like it and I
> can't figure it out.
>
I'm trying to check for a directory and create it if it doesn't exist as
follows:
CommonDir="../common"
if [ -d ${CommonDir} ]; then
mkdir "${CommonDir}"
fi
It works from the command line, but my script doesn't seem to like it and I
can't figure it out.
Thanks for any help,
Duane
--
View th
Sorry, Bob, it's my bad. ${HOME} in my previous posts were not described
consistently. Actually my $HOME on my office server is "/cis/home/tingli".
"'/cis/home/tingli/bin/bash-3.2.48/bin/bin/bash'" is actually where my new
bash executable lies in the server (the double bins were left from my sill
On Thu, 2009-03-05 at 13:47 -0500, Greg Wooledge wrote:
>
> That might be a little more heavy-handed than you were looking for,
> but since you're already hitting /tmp it shouldn't be terrible to add
> a FIFO there.
Yeah. I really didn't want to use a named pipe for this.
Thanx for the help tho
On Thu, Mar 05, 2009 at 12:28:00PM -0500, Brian J. Murrell wrote:
> tar cf - /etc | tar xf - | tee /tmp/outfile
> I want (specifically) the second
> tar command to run in the background and I want to wait for it so that
> the "trap" in the parent shell can process signals. Altogether I want:
>
lehe wrote:
> Lately I am trying to install a higher version of emacs under my ${HOME} on
> my office server. I add the new emacs path into PATH. It works quite well
> when I ssh to the server, but encounters this "/home/emacs/bin/emacs: cannot
> execute binary file" error when I am working on my o
Hi,
I want to effect this pipeline:
tar cf - /etc | tar xf - | tee /tmp/outfile
manually. It seems that some form of file descriptor manipulation (i.e.
moving, duplication, etc.) should be able to achieve this, but I can't
seem to figure it out.
Why would I want to do this? Because I want (sp
lehe wrote:
> As to changing to new bash from the beginning, I added into .bash_profile:
> "SHELL='/cis/home/tingli/bin/bash-3.2.48/bin/bin/bash'
> exec $SHELL "
> It works quite well. The new bash starts automatically if I ssh to the
> server from my laptop.
Good. Is there really two "/bin/bin/"
Hi,
Lately I am trying to install a higher version of emacs under my ${HOME} on
my office server. I add the new emacs path into PATH. It works quite well
when I ssh to the server, but encounters this "/home/emacs/bin/emacs: cannot
execute binary file" error when I am working on my office computer
Thanks Bob!
I get my bashdb in my emacs work already.
As to changing to new bash from the beginning, I added into .bash_profile:
"SHELL='/cis/home/tingli/bin/bash-3.2.48/bin/bin/bash'
exec $SHE
10 matches
Mail list logo