02-01-2010
he stop on this question
" puts -nonewline "\nVoce gostaria de continuar ou modificar lista?(y/n/m): "
and exit without change password.
10 More Discussions You Might Find Interesting
1. AIX
hi guys
i have such simple script, which i'm executing on AIX 5.3
#!/usr/local/bin/expect
spawn passwd exptest
set password 123
expect "*password:*"
send "$password\r"
expect "*password again:*"
send "$password\r"
expect eof
the output is following:
spawn passwd exptest
sh:... (4 Replies)
Discussion started by: zoom
4 Replies
2. Shell Programming and Scripting
Hello all you scripting Gurus,
I have an expect script that gets called from an AppleScript Studio app that basically takes arguments for user name, password, and server address and then calls rsync. Everything works wonderfully, EXCEPT (there had to be one of those) if the user name starts... (4 Replies)
Discussion started by: jdyck
4 Replies
3. AIX
Hi,
I am facing a strange problem while executing a script from a solaris server. This script calls another one to execute "expect" commands on some other 40 servers (all AIX 5200). I am passing username and password to the "expect" script as arguments. My problem is that it is showing the... (4 Replies)
Discussion started by: gsabarinath
4 Replies
4. UNIX for Dummies Questions & Answers
Hi
I'm writing a script which calls an expect script to retrieve configuration files for network devices. I want to avoid using TFTP to transfer the configs if possible and so I'm redirecting the screen output to a text file.
This is the expect script:
#!/usr/local/bin/expect
set... (2 Replies)
Discussion started by: Ant1815
2 Replies
5. Shell Programming and Scripting
hello All,
I am doing SFTP using expect. We just change our server from sun solaris 8 to sun solaris 10.
The script was working good on sun solaris 8.
But it is giving problem on 10. from shell, SFTP is working fine.Please help me.
What can be the problem.
LIB_sftp_get()
{
... (0 Replies)
Discussion started by: mindtee_abhi
0 Replies
6. UNIX for Dummies Questions & Answers
Hi Im writing an expect program for automating ftp. Having trouble with mget:
expect "ftp>" {send "mget *.txt\r"}
expect "mget*?" {send "n\r" ; expect_continue}
expect "ftp>" {send "bye\r"}
But expect even on ftp prompt "n" gets sent
Please help... (1 Reply)
Discussion started by: crackle1985
1 Replies
7. Shell Programming and Scripting
Hi,
Have strange problem.
When I run an expect script towards a switch, it will not work.
$ ./test2
spawn ssh admin@sesafdd101
Password:
Last login: Thu Dec 25 13:20:54 2008 from 172.20.96.14
ECN430/330/212 Linux, based on Wind River Linux glibc_small (standard) 2.0
Trying... (1 Reply)
Discussion started by: etxnreg
1 Replies
8. Shell Programming and Scripting
i have written simple expect script but it doesnt work the way that i want can someone suggest wat is the issue?
#!/usr/bin/expect
spawn ssh abc@abc
expect "password:"
send "xyz\r"
expect "$"
send "mkdir hello\r"
#sleep 10
#exit 0
output
---------------
it does not create directory... (4 Replies)
Discussion started by: bkumar82
4 Replies
9. Shell Programming and Scripting
expect {
-re "(.*)NEXT PAGE(.*)" {
send "\r\n"
}
exp_continue (0 Replies)
Discussion started by: sagar_1986
0 Replies
10. Shell Programming and Scripting
Hey there :)
I have a Bash Script and I'm trying to update Roundcube, but theres a user interactive line like:
bin/installto.sh /var/www/mail/rc
Upgrading from 1.1.3. Do you want to continue? (y/N)
I'm trying to avoid this user interaction like this:
cd roundcubemail-1.2.1 >/dev/null... (5 Replies)
Discussion started by: Aeris
5 Replies
puts(n) Tcl Built-In Commands puts(n)
__________________________________________________________________________________________________________________________________________________
NAME
puts - Write to a channel
SYNOPSIS
puts ?-nonewline? ?channelId? string
_________________________________________________________________
DESCRIPTION
Writes the characters given by string to the channel given by channelId.
ChannelId must be an identifier for an open channel such as a Tcl standard channel (stdout or stderr), the return value from an invocation
of open or socket, or the result of a channel creation command provided by a Tcl extension. The channel must have been opened for output.
If no channelId is specified then it defaults to stdout. Puts normally outputs a newline character after string, but this feature may be
suppressed by specifying the -nonewline switch.
Newline characters in the output are translated by puts to platform-specific end-of-line sequences according to the current value of the
-translation option for the channel (for example, on PCs newlines are normally replaced with carriage-return-linefeed sequences. See the
fconfigure manual entry for a discussion on ways in which fconfigure will alter output.
Tcl buffers output internally, so characters written with puts may not appear immediately on the output file or device; Tcl will normally
delay output until the buffer is full or the channel is closed. You can force output to appear immediately with the flush command.
When the output buffer fills up, the puts command will normally block until all the buffered data has been accepted for output by the oper-
ating system. If channelId is in nonblocking mode then the puts command will not block even if the operating system cannot accept the
data. Instead, Tcl continues to buffer the data and writes it in the background as fast as the underlying file or device can accept it.
The application must use the Tcl event loop for nonblocking output to work; otherwise Tcl never finds out that the file or device is ready
for more output data. It is possible for an arbitrarily large amount of data to be buffered for a channel in nonblocking mode, which could
consume a large amount of memory. To avoid wasting memory, nonblocking I/O should normally be used in an event-driven fashion with the
fileevent command (do not invoke puts unless you have recently been notified via a file event that the channel is ready for more output
data).
EXAMPLES
Write a short message to the console (or wherever stdout is directed):
puts "Hello, World!"
Print a message in several parts:
puts -nonewline "Hello, "
puts "World!"
Print a message to the standard error channel:
puts stderr "Hello, World!"
Append a log message to a file:
set chan [open my.log a]
set timestamp [clock format [clock seconds]]
puts $chan "$timestamp - Hello, World!"
close $chan
SEE ALSO
file(n), fileevent(n), Tcl_StandardChannels(3)
KEYWORDS
channel, newline, output, write
Tcl 7.5 puts(n)