I have the following expect script, which I want to run in cron. It fails however, very likely due to the fact that there's no /dev/tty available.
set timeout 30
spawn -nottycopy -nottyinit /usr/bin/ssh $hostname $command
match_max 100000
expect "password"
send -- "$password"
send -- "\r"... (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)
I'm calling an expect script via a ksh script in cron and it is failing. The script runs fine if i run it manually. Does anyone know if it is an issue with compatibilty and if there is a way around it? (2 Replies)
Hi,
I am running some etl commands in the windows from shell script(from unix sun solaris 5.9) by using expect package .While running manually the script is working fine.While running from cron it is exiting the after successfully firing the ETL command(The control does not stop after firing... (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)
My searches turned up nothing relevant, so I apologize if this has already been looked at.
I am trying to run an expect script from a Solaris machine, that ssh's into an AIX machine, and interacts with a SMIT created menu system that runs a few backups for me.
The expect script runs fine when... (0 Replies)
I wrote a script to download the files from sftp location to local. while running the script manually its working fine. when i schedule the same in cron its not working.... :wall::wall:
here is the script:
#!/bin/bash
... (2 Replies)
My cron file. Copied $PATH
# Minute Hour Day of Month Month Day of Week Command
SHELL=/bin/ksh
PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/perl/lib:/perl/lib/lib/perl5:/perl/scripts:.:/perl/lib/local:/home/popeye:/temp
0... (3 Replies)
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)
Hello All,
I'm having an issue getting an expect script to run as a cron job. The script executes fin if I run it from the command line but I get nothing when trying to run it as a cron job. I've researched other forums and threads and there have been references to the environment, or lack... (16 Replies)
Discussion started by: KingT617
16 Replies
LEARN ABOUT BSD
chfn
CHPASS(1) General Commands Manual CHPASS(1)NAME
chpass - add or change user database information
SYNOPSIS
chpass [ -a list ] [ user ]
DESCRIPTION
Chpass allows editing of the user database information associated with user or, by default, the current user. The information is formatted
and supplied to an editor for changes. The vi editor will be used unless the environmental variable EDITOR selects an alternate editor.
When the editor terminates, the information is re-read and used to update the user database itself. Only the user, or the super-user, may
edit the information associated with the user.
Only the information that the user is allowed to change is displayed.
Possible display items are as follows:
Login: user's login name
Password: user's encrypted password
Uid: user's id
Gid: user's login group id
Change: password change time
Expire: account expiration time
Class: user's general classification
Home Directory: user's home directory
Shell: user's login shell
Full Name: user's real name
Location: user's normal location
Home Phone: user's home phone
Office Phone: user's office phone
The login field is the user name used to access the computer account.
The password field contains the encrypted form of the user's password.
The uid field is the number associated with the login field. Both of these fields should be unique across the system (and often across a
group of systems) as they control file access.
While it is possible to have multiple entries with identical login names and/or identical user id's, it is usually a mistake to do so.
Routines that manipulate these files will often return only one of the multiple entries, and that one by random selection.
The group field is the group that the user will be placed in upon login. Since this system supports multiple groups (see groups(1)) this
field currently has little special meaning. This field may be filled in with either a number or a group name (see group(5)).
The change field is the date by which the password must be changed.
The expire field is the date on which the account expires.
Both the change and expire fields should be entered in the form ``month day year'' where month is the month name (the first three charac-
ters are sufficient), day is the day of the month, and year is the year.
The class field is currently unused. In the near future it will be a key to a termcap(5) style database of user attributes.
The user's home directory is the full UNIX path name where the user will be placed on login.
The shell field is the command interpreter the user prefers. If the shell field is empty, the Bourne shell (/bin/sh) is assumed.
When altering a login shell, and not the super-user, the user must select an approved shell from the list in /etc/shells.
The last four fields are for storing the user's full name, office location, and home and work telephone numbers.
The super-user is also allowed to directly supply a user database entry, in the format specified by passwd(5), as an argument to the -a
option. This argument must be a colon (``:'') separated list of all the user database fields, although they may be empty.
Once the information has been verified, chpass uses mkpasswd(8) to update the user database. This is run in the background, and, at very
large sites could take several minutes. Until this update is completed, the password file is unavailable for other updates and the new
information will not be available to programs.
FILES
/etc/master.passwd The user database /etc/shells The list of approved shells
SEE ALSO login(1), finger(1), getusershell(3), passwd(5), mkpasswd(8), vipw(8)
Robert Morris and Ken Thompson, UNIX password security
BUGS
User information should (and eventually will) be stored elsewhere.
4th Berkeley Distribution March 12, 1989 CHPASS(1)