Difference between using Here document and Expect in scripts
Hi,
I am confused between using here document and using expect for writing interactive shell scripts(like changing password ,FTP or doing su).
My questions are :
1)Why here documents cant change password from shell script.
2)Why we need to use expect for same?
3) Can Sourcing a script can do FTP or change password? like
Code:
. myscript.ksh
or
Code:
source myscript.ksh
4) What is the difference in all three behaviors(here,expect and source)?
Tried to resolve these on own but still i am confused.
Hi,
First, let me explain the issue I am trying to solve. We have a lot of expect scripts with the duplicated send/expect commands. So, I'd like to be able to extract the duplicated code into the common scripts that can be used by other scripts.
Below is my test where I am trying to call... (0 Replies)
Hi
I am getting some errors when i am running the shell script using the following syntax:
>abc.sh
but the same script works fine with the following syntax:
>sh abc.sh
wats the difference in both....please help
thanks in advance. (6 Replies)
What is the difference between calling the sub scripts of below two line.
/home/scripts/devdb.sh
. /home/scripts/devdb.sh
sh /home/scripts/devdb.sh
We are using the suse 2.0 version (4 Replies)
Hi
I would like to know how to handle my script that expects an input when calling the script and the user doesn't enter anything, I need to re-direct to my helpfile.
Bascically here is my script:
#!/bin/bash
csvdir="/var/local/dsx/csv/general"
csvfile="$csvdir/$csvfile"... (3 Replies)
hi all,
i have this script that accepts passwords automatically and its working in one host only. my problem is how will i use it if i need it to run in more than one host/server let say by using "for loop statement"
working :
spawn bundle linux -r hostname checkpath... (2 Replies)
Hi,
I have perl script abc.pl which runs perfectly fine on windows ( execution from cmd).
Now i tried to execute the same perl module on the AIX server after defining the captureoutput.pm and other relevant changes.
But its behaving very weirdly as a portion of the URL which is formed by... (3 Replies)
Hello all,
I've been trying to design a script which will help me transfer files from one unix box to another. Following is the code:
#!/usr/local/bin/expect
spawn /usr/bin/scp ms_cp5_daily.ksh userid@cat:/prod/env/ms.txt
set pass xxxxxx
expect {
password: {send "$pass\r";... (4 Replies)
I have a bash script on server that runs fine when run interactively and writes stderr output to a file.
However, when invoked through a 'expect' script run on Mac OS my laptop which does ssh to the server : generates the expected file, but file has no content. I suspect the stderr is getting... (1 Reply)
Hello... and thanks in advance for reading this or offering me any assistance
I'm trying to understand specific differences between the various login scripts... I understand the differences between interactive vs non-interactive and login vs non-login shells... and that's not where my question... (4 Replies)
Discussion started by: bodisha
4 Replies
LEARN ABOUT HPUX
newgrp
newgrp(1) General Commands Manual newgrp(1)NAME
newgrp - switch to a new group
SYNOPSIS
[group]
DESCRIPTION
The command changes your group ID without changing your user ID and replaces your current shell with a new one.
If you specify group, the change is successful if group exists and either your user ID is a member of the new group, or group has a pass-
word and you can supply it from the terminal.
If you omit group, changes to the group specified in your entry in the password file,
Whether the group is changed successfully or not, or the new group is the same as the old one or not, proceeds to replace your current
shell with the one specified in the shell field of your password file entry. If that field is empty, uses the POSIX shell, (see sh-
posix(1)).
If you specify (hyphen) as the first argument, the new shell starts up as if you had just logged in. If you omit the new shell starts up
as if you had invoked it as a subshell.
You remain logged in and the current directory is unchanged, but calculations of access permissions to files are performed with respect to
the new real and effective group IDs.
Exported variables retain their values and are passed to the new shell. All unexported variables are deleted, but the new shell may reset
them to default values.
Since the current process is replaced when the new shell is started, exiting from the new shell has the same effect as exiting from the
shell in which was executed.
EXTERNAL INFLUENCES
International Code Set Support
Characters from the 7-bit USASCII code set are supported in group names (see ascii(5)).
DIAGNOSTICS
The command issues the following error messages:
Your user ID does not qualify as a group member.
The group name does not exist in
If a password is required, it must come from a terminal.
Standard input is not a terminal file,
causing the new shell to fail.
EXAMPLES
To change from your current group to group without executing the login routines:
To change from your current group to group and execute the login routines:
WARNINGS
There is no convenient way to enter a password into
The use of group passwords is not recommended because, by their very nature, they encourage poor security practices. Group passwords may
be eliminated in future HP-UX releases.
If the specified group to has multiple inconsistent entries (i.e. the group id or/and password are different) in the group database, will
consider the group id and password of the first matched group entry as the correct group id and password for the group.
FILES
System group file
System password file
SEE ALSO csh(1), ksh(1), login(1), sh-posix(1), group(4), passwd(4), environ(5).
STANDARDS CONFORMANCE newgrp(1)