Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: problems faced while using ssh

Subject: Re: problems faced while using ssh
Date: Thu, 14 Dec 2006 07:29:35 -0500
On Tue, Dec 12, 2006 at 10:10:43PM -0800, kknegi wrote:
C:\>ssh shadm@hpcc558.corp.hp.com /home/shadm/shcalc/DateProject/test.sh >
test1.log

What does this script look like?

grep: can't open rates.rel

You realize that the script will be executed with its working directory
set to shadm's $HOME, correct?

expr: Syntax error

Most likely, you forgot to quote something properly.  In general, I
abhor the use of expr(1) in shell scripts.  Its only real purpose is
in writing legacy (pre-POSIX, pre-ksh) Bourne shell scripts.  There
are shell builtins that can do almost everything expr does, but faster
and cleaner.

grep: can't open canada_exchange_rate.txt
grep: can't open month_midmonth_release.txt
sed: Cannot find or open file month_midmonth_release.txt.

I think the fact that you're sitting in $HOME instead of wherever you
expected to be is the most likely candidate for all three of these.

Is there something to do with SSH permissions????

Sounds more like you need a few pointers in writing shell scripts.

<Prev in Thread] Current Thread [Next in Thread>