04-20-2012
Yes, just like any other UNIX program or script file.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hello. i'm attempting to use minicom in linux, but i'm having some difficulties. When i type in "minicom", the application opens up. It says 'starting minicom/finding modem'(something like that). However, once it actually starts, I can't do anything. No matter what I type in, it doesn't work. ... (2 Replies)
Discussion started by: kickboxer
2 Replies
2. UNIX for Dummies Questions & Answers
Does anyone have a working minicom script they would care to post as I can't get the scripting working and the scriptdemo and unixlogin sample scripts are on my system either.
Thanx,
I (2 Replies)
Discussion started by: ianf
2 Replies
3. Shell Programming and Scripting
Hi,
I am new to use minicom. I want script to run on minicom with username and password as automated.(Expect). please could anyone suggest the sample code for it.
Thanks in advance (2 Replies)
Discussion started by: vanid
2 Replies
4. Shell Programming and Scripting
Hi,
I am new to using minicom. I want how to write a expect script for minicom login? I wrote a code but its not acting what iam expecting. here I have my code:
#!/usr/bin/expect
set fd
fconfigure $fd
spawn -open $fd
spawn minicom
expect “enter:”
send "\n"
send "\n"
... (3 Replies)
Discussion started by: vanid
3 Replies
5. Shell Programming and Scripting
Hi all,
I have some trouble getting stty to talk to some serial/usb converter.
Getting minicom to work was however quite simple after I entered the following settings in addition to its standard-setup:
pu port /dev/ttyUSB0
pu baudrate 19200
pu bits 8
pu... (3 Replies)
Discussion started by: pa-trick
3 Replies
6. Shell Programming and Scripting
This is what I've tried:
#!/bin/sh
send sh
send showifs
send exit
! killall minicom
My problem is that for some reason when I do this it doesn't give me the results of the prior commands sent like showifs
So I suspect my syntax is wrong. (1 Reply)
Discussion started by: uradunce
1 Replies
7. Shell Programming and Scripting
I'm a fairly new user to Linux based systems and am still a little uncomfortable with using the command interface. I'm trying to get my feet wet but have unfortunately hit a wall and am actually not even sure what I am trying to accomplish is at all possible.
Basically, I am trying to use a... (0 Replies)
Discussion started by: nrdk00
0 Replies
8. Shell Programming and Scripting
Hi All,
I am testing expect script in command prompt without issue, but in crontab it is not working, i check the output error as below:
#cat /var/log/testexp.log
spawn minicom -C /var/log/minicom1.log
No cursor motion capability (cm)
AT+COPS=?
I am new in scripting, together... (1 Reply)
Discussion started by: elingtey
1 Replies
9. SCO
hello is there a copy of minicom or equivalent for unixware 7?
thanks (3 Replies)
Discussion started by: deus-programmer
3 Replies
10. UNIX for Dummies Questions & Answers
Hey All,
I am trying to find something similar to minicom, but it needs the ability to be ran during a remote dialup session on the remote
device's side.
If I dial into the remote server (*using minicom) and then try to run minicom on the remote server I get the following:
# minicom... (20 Replies)
Discussion started by: mrm5102
20 Replies
log(8) System Manager's Manual log(8)
NAME
log - Records input and output from a program
SYNOPSIS
/usr/sbin/log <logfile> <command>
OPERANDS
The file in which to record the interaction being logged. The command to execute.
DESCRIPTION
The log program runs <command> and logs the input to and output from <command> to the <logfile> file. Input and output are logged until
<command> exits, the log program exits, and the exit status of <command> is returned.
The log program is used by the system installation procedure and the it(8) command to create the /var/adm/smlogs/install.log and
/var/adm/smlogs/it.log installation log files.
RESTRICTIONS
Because the log program is used in the installation standalone environment, program size was the greatest concern in its implementation.
The log program does not search for the PATH variable to locate <command> and error messages are terse.
The log program causes <command> to take standard input from and write standard output and standard error to UNIX pipes. Some commands
will not be able to operate in this environment; therefore, it is suggested that you use the script(1) command instead. UNIX shells will
not issue prompts when run from log unless the shell is started with an explicit interactive switch (-i for most shells). For example, log
foo.tmp /sbin/sh -i
In the previous example, foo.tmp is the name of <logfile>.
The log program intercepts end-of-file (usually Ctrl/d). Therefore programs which normally receive end-of-file as an exit command must
exit by some other means.
ERRORS
Log open error
Explanation:
The log program was unable to open <logfile>. Verify that the directory exists and that ownerships and permissions are set correctly.
Exec Error
Explanation:
The log program was unable to execute <command>. Verify that you specified a full pathname for <command> and that <command> is an exe-
cutable file.
Fork Error
Explanation:
The log program was unable to create one of the processes it requires to log data.
SEE ALSO
Commands: it(8), script(1)
log(8)