Hi,
I am writing a script to automate installation of java in shell script.
I am getting the following error while executing this script
Spawn is working to other ssh script at the same server.
Can anyone let me why these errors are ?
Thanks
Last edited by Franklin52; 01-14-2015 at 09:58 AM..
Reason: Please use code tags
hello all
im trying to use in sun Solaris the information received from the top command
now i several machines that dont have install the top program so when im running the script im geting error
saying after im running this code :
set MemoryInfo = `top | grep Memory`
if (... (2 Replies)
Hi,
I'm very new to UNIX.
I need to FTP a file to a remote host. It happens through a port 2222.I need to automate the process as the SCP command prompts for a password.
1) The regular ftp, tells me that the connection is refused
2) The sftp login@remotehost
gives me... (0 Replies)
I need to run the spawn command but when I typed it in, I got
"ksh: spawn: not found".
So, I downloaded spawn-fcgi but it required to be compiled first. The compile failed when I tried it. I need a copy that's ready to be used.
Unix system info:
OS: Sun Solaris 2.8
Shell: ksh
Does... (4 Replies)
Hi Experts,
I hav a question for you..
Can we open a new window(SunOS 5.10,Putty) by a unix_command from the one we're on? Is it possible?
Thanks. (2 Replies)
Can 'spawn' script be used more than once in a given expect script ??
What I'm trying to do is, first log-into a remote server through one 'ssh' spawn com and then from there log-into another server using a secod 'ssh' spawn command. But this approach is not working... the second ssh attempt... (1 Reply)
I am running the export command within a view to use that value inside my build script. But while executing it it is saying "export command not found"
My code is as follows:
--------------------------
#!/bin/sh
user="test"
DIR="/bldtmp/"$user
VIEW="test.view1"
echo "TMPDIR before export... (4 Replies)
Hi all,
I have a script that runs sftp with expect so I can login and send a file in a cronjob. I've installed this on a couple other servers and it has been fine. However, this time on this machine, it seems to be giving me an issue. It won't move past the spawn sftp command and return a... (3 Replies)
Hi all,
I want to run the following command from my main prompt :
# spawn bash
but I get the following error:
spawn: Command not found.
For this to work , I first have to go into expect.
#expect
expect1.1>spawn bash
spawn bash
564
expect1.2>
Is there any way I can skip the... (2 Replies)
spawn ssh oracle@$myserver $mycommand
match_max 100000
expect "*?assword:*"
send "$v_password\r"
send "\r"
expect eof
I run this code above and got the error.
spawn: fatal: do not run this command by hand
Thanks (3 Replies)
Discussion started by: zam
3 Replies
LEARN ABOUT DEBIAN
checkbashisms
CHECKBASHISMS(1) General Commands Manual CHECKBASHISMS(1)NAME
checkbashisms - check for bashisms in /bin/sh scripts
SYNOPSIS
checkbashisms script ...
checkbashisms --help|--version
DESCRIPTION
checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
of bashisms. It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.
Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported by POSIX";
this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.
In cases where POSIX and Debian Policy disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
options for stricter checking.
OPTIONS --help, -h
Show a summary of options.
--newline, -n
Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)
--posix, -p
Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).
--force, -f
Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
to be a shell wrapper).
--extra, -x
Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
tive which may be ignored. For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.
--version, -v
Show version and copyright information.
EXIT VALUES
The exit value will be 0 if no possible bashisms or other problems were detected. Otherwise it will be the sum of the following error val-
ues:
1 A possible bashism was detected.
2 A file was skipped for some reason, for example, because it was unreadable or not found. The warning message will give details.
SEE ALSO lintian(1).
AUTHOR
checkbashisms was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
Julian Gilbey <jdg@debian.org>.
DEBIAN Debian Utilities CHECKBASHISMS(1)