12-04-2008
Output terminal sessions to screen and log file
I would like to use a terminal session to ssh to switches and routers. I need to capture data while logged into switches to a file I can email for troubleshooting.
I use termial to log into Cisco switch, run the sh tech command, and then sent the output to cisco. Is there a way to run a script which will allow me to capture the sh tech output to a file. I am currently using the tcsh shell.
I am new to shell scripting so a good explaination would be greatly appreciated.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello
a few Q's that if anyone knows the answer to i would be grateful:
:confused: when exiting a terminal session run through a windows environment i can either type exit or use ctrl +D. I was wondering if one way was a 'cleaner' method to exit then the other or whether it is executed the... (2 Replies)
Discussion started by: hu$h
2 Replies
2. UNIX for Dummies Questions & Answers
Being new to screen I am having real trouble with some basics.
Actually when I login to a machine and type
sharan :: screen -list
I see the following There are screens on:
11001.pts-11.hcllnx2 (Attached)
10615.pts-11.hcllnx2 (Attached)
2 Sockets in... (0 Replies)
Discussion started by: sharanbr
0 Replies
3. Shell Programming and Scripting
I want to output screen messages to a logfile when executing an automated script. I have tried the script and command to do this but with no luck.
Thanks,
Nicole (5 Replies)
Discussion started by: nsutti
5 Replies
4. Shell Programming and Scripting
Hi,
I would need to log the whole screen ouput to a log file.
All Inputs from the Agent, all echo´s and DBMS Outputs from the PL/SQL.
Basicly everything what I can see during the run on the screen.
I tried it already with
#exec 2>$BASELOG/RUN.log
#exec 1>$BASELOG/RUN.log
#exec >... (1 Reply)
Discussion started by: enjoy
1 Replies
5. UNIX for Dummies Questions & Answers
Hi I am working in Solaris 10 and I want to monitor logs for every telnet/ssh session that tries to connect to the server. I need these logs to be generated in a file that I can fetch using ftp.
I am a new user and a stepwise detail will be great
BR
saGGee (3 Replies)
Discussion started by: saggee
3 Replies
6. Shell Programming and Scripting
Hi,
I would normally clear off the history entries from a terminal by using the following commands:
> ~/.bash_history
history -c
But this will remove the entries of that particular session only. How to prune all the entries of all login sessions for a particular user in a system?
N.B:... (3 Replies)
Discussion started by: royalibrahim
3 Replies
7. Shell Programming and Scripting
I am trying to get following result from the scipt I have. First time it generates the o/p in correct format. However if I run it again it appends to the existing file. I would like to see o/p on screen as well as save it in file. Everytime it should create new file.
## I/P file
0174
0175... (3 Replies)
Discussion started by: dynamax
3 Replies
8. Solaris
Admins,
We have a strange problem on our solaris zones. We have four zones on a Global server (Sun-Fire-V890; Solaris 10 Update 6) and the SSH sessions to all four zones are terminated at a specific time (11:10 PM) every night. The SSH session to the global server is not terminated.
Also, any... (1 Reply)
Discussion started by: yogijp
1 Replies
9. Shell Programming and Scripting
Hello All,
I have a text file containing output from a command that contains lots of escape/control characters that when viewed using vi or view, looks like jibberish. But when viewed using the cat command the output is formatted properly.
Is there any way to take the output from the cat... (7 Replies)
Discussion started by: mrm5102
7 Replies
10. UNIX for Beginners Questions & Answers
Hi All,
I am trying to out of shell script when i run it
like
sh /mypath/abc.sh
....a screen log should be generated whenever i input the values, when above the script prompt for values
Regards
Amarendra (3 Replies)
Discussion started by: amar1208
3 Replies
DDB(8) BSD System Manager's Manual DDB(8)
NAME
ddb -- configure DDB kernel debugger properties
SYNOPSIS
ddb capture [-M -core] [-N -system] print
ddb capture [-M -core] [-N -system] status
ddb script scriptname
ddb script scriptname=script
ddb scripts
ddb unscript scriptname
ddb pathname
DESCRIPTION
The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily
via sysctl(8) MIB entries.
To ease configuration, commands can be put in a file which is processed using ddb as shown in the last synopsis line. An absolute pathname
must be used. The file will be read line by line and applied as arguments to the ddb utility. Whitespace at the beginning of lines will be
ignored as will lines where the first non-whitespace character is '#'.
OUTPUT CAPTURE
The ddb utility can be used to extract the contents of the ddb(4) output capture buffer of the current live kernel, or from the crash dump of
a kernel on disk. The following debugger commands are available from the command line:
capture [-M core] [-N system] print
Print the current contents of the ddb(4) output capture buffer.
capture [-M core] [-N system] status
Print the current status of the ddb(4) output capture buffer.
SCRIPTING
The ddb utility can be used to configure aspects of ddb(4) scripting from user space; scripting support is described in more detail in
ddb(4). Each of the debugger commands is available from the command line:
script scriptname
Print the script named scriptname.
script scriptname=script
Define a script named scriptname. As many scripts contain characters interpreted in special ways by the shell, it is advisable to
enclose script in quotes.
scripts
List currently defined scripts.
unscript scriptname
Delete the script named scriptname.
EXIT STATUS
The ddb utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
The following example defines a script that will execute when the kernel debugger is entered as a result of a break signal:
ddb script kdb.enter.break="show pcpu; bt"
The following example will delete the script:
ddb unscript kdb.enter.break
For further examples, see the ddb(4) and textdump(4) manual pages.
SEE ALSO
ddb(4), textdump(4), sysctl(8)
HISTORY
The ddb utility first appeared in FreeBSD 7.1.
AUTHORS
Robert N M Watson
BUGS
Ideally, ddb would not exist, as all pertinent aspects of ddb(4) could be configured directly via sysctl(8).
BSD
December 24, 2008 BSD