I need to run a remote application(GUI) in a client.i.e on running a script in the client machine i should get the GUI application which is running in the server by providing password through the script.Will expect or autoexpect command suit for this scenario?
could anyone help me by posting some... (0 Replies)
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)
Hello to all...this is my first post (so please go easy). :)
I feel pretty solid at expect scripting, but I'm running into an issue that I'm not able to wrap my head around. I wrote a script that is a little advanced for logging into a remote Linux machine and changing text in a file using sed.... (2 Replies)
Hello hello, did a quick search and didn't turn up anything helpful. I've got a book I'm sure has the answers, but I don't think I'll have time to finish it before this all has to work, so here goes~ if this isn't a good place to post and someone could direct me to another forum I'd appreciate... (1 Reply)
This Expect script provides expect with a list of IP addresses to Cisco IPS sensors and commands to configure Cisco IPS sensors. The user, password, IP addresses, prompt regex, etc. have been anonymized. In general this script will log into the sensors and send commands successfully but there are... (1 Reply)
Hello All,
I am trying to automate an installation process using expect and sh script. My problem is that during the installation process the expected value can change according to the situation.
For Example if this is a first time installation then at step 3 I'll get "Do you want to accept... (0 Replies)
Hi,
Am very new to expect scripting..
Can You please suggest me how to call an expect script inside another expect script..
I tried with
spawn /usr/bin/ksh
send "expect main.exp\r"
expect $root_prompt
and
spawn /usr/bin/ksh
send "main.exp\r"
expect $root_prompt
Both... (1 Reply)
I have an expect script called remote that I want to call from inside my expect script called sudoers.push, here is the code that is causing me issues:
set REMOTE "/root/scripts/remote"
...
log_user 1
send_user "Executing remote script as $user...\n"
send_user "Command to execute is: $REMOTE... (1 Reply)
I'm fairly new to scripting so this might not be possible.
I am using Expect with Cisco switches and need to capture the string after finding the expect request. For example, when I issue "show version" on a Nexus switch, I'm looking to capture the current firmware version:
#show version
... (0 Replies)
Hi All,
i am trying to ssh to a remote machine and execute certain command to remote machine through script.
i am able to ssh but after its getting hung at the promt and after pressing ctrl +d i am gettin the out put as
expect: spawn id exp5 not open
while executing
"expect "$" {... (3 Replies)
Discussion started by: Siddharth shivh
3 Replies
LEARN ABOUT SUSE
ypchsh
yppasswd(1) General Commands Manual yppasswd(1)NAME
yppasswd, ypchfn, ypchsh - change your password in the NIS database
SYNOPSIS
yppasswd [-f] [-l] [-p] [user]
ypchfn [user]
ypchsh [user]
DESCRIPTION
In the old days, the standard passwd(1), chfn(1) and chsh(1) tools could not be used under Linux to change the users NIS password, shell
and GECOS information. For changing the NIS information, they were replaced by their NIS counterparts, yppasswd, ypchfn and ypchsh.
Today, this versions are deprecated and should not be used any longer.
Using the command line switches, you can choose whether to update your password -p, your login shell -l, or your GECOS field -f, or a com-
bination of them. yppasswd implies the -p option, if no other option is given. If you use the -f or -l option, you also need to add the -p
flag. ypchfn implies the -f option, and ypchsh -l.
When invoked without the user argument, the account information for the invoking user will be updated, otherwise that of user will be
updated. This option is only available to the super-user. If the yppasswdd daemon on the server supports it, you can give the root password
of the server instead of the users [old] password.
All tools will first prompt the user for the current NIS password needed for authentication with the yppasswdd(8) daemon. Subsequently, the
program prompts for the updated information:
yppasswd or -p
Change the user's NIS password. The user is prompted for the new password. While typing the password, echoing is turned off, so
the password does not appear on the screen. An empty password is rejected, as are passwords shorter than six characters. The user
will then be requested to retype the password to make sure it wasn't misspelled the first time.
ypchsh or -l
Change the user's login shell. The user is prompted for a new shell, offering the old one as default:
Login shell [/bin/sh]: _
To accept the default, simply press return. To clear the shell field in your passwd(5) file entry (so that the system's default
shell is selected), enter the string none.
ypchfn or -f
Change the user's full name and related information. Traditionally, some applications expect the GECOS field (field 4) of the
passwd(5) file to contain the user's real name (as opposed to the login name) plus some additional information like the office phone
number. This information is displayed by finger(1) and probably some other tools, too.
When setting the full name, ypchfn displays the following prompts, with the defaults in brackets:
Name [Joe Doe]:
Location [2nd floor, bldg 34]:
Office Phone [12345]:
Home Phone []:
To accept a default, simply press return. To clear a field, enter the string none.
SEE ALSO chfn(1), chsh(1), finger(1), passwd(5), passwd(1), ypcat(1), yppasswdd(8), ypserv(8), ypwhich(1)AUTHOR
yppasswd is part of the yp-tools package, which was written by Thorsten Kukuk <kukuk@linux-nis.org>.
YP Tools 2.12 April 2010 yppasswd(1)