How To Capture PUTTY Session Log
PuTTY is a free implementation of Telnet and SSH for Win32 and Unix platforms, along with an xterm terminal emulator. It is written and maintained primarily by Simon Tatham.
Here I would like to share How To Capture PUTTY Session Log.
1. To capture a session with PuTTY, open up a PUTTY.
2. Look for Category Session -> Logging
3. Under Session Logging, choose “All session output” and key in your desire log filename(default is putty.log).
4. This should create the file in the location you choose and start loggin everyting from the session.
5. For capture Cisco Router or Switches(I tried with Nexus 1000V on VMware vSphere), type ’show running-config’.
Read more
Possibly Related Posts:
- How to Add Date And Time To Your Bash History on SuSE Linux
- RPM Segmentation Fault
- Introduce Server Fault
- OpenVPN route issue
- How to clean EMC CX 3-80 Dirty Cache?
How to Add Date And Time To Your Bash History on SuSE Linux
The SuSE Linux Enterpise 10 which came together with bash-3.x RPM and HISTORY command show insufficient information(at least for me) as example below:
1 vi /etc/hosts
2 rpm -qa|grep bash
3 cat /etc/SuSE-release
4 history
For any SuSE Linux Enterprise server 10 that managed by more than one people, I would suggest you should make history command more user friendly and more information for auditing purposes.
Edit /etc/bash.bashrc and append to the bottom:
export HISTTIMEFORMAT="%h/%d - %H:%M:%S "
save it.
Read more
Possibly Related Posts:
- How To Capture PUTTY Session Log
- RPM Segmentation Fault
- Introduce Server Fault
- OpenVPN route issue
- How to clean EMC CX 3-80 Dirty Cache?
RPM Segmentation Fault
While I was try to upgrade one of the RPM package on SuSE Linux Server, I’m getting an error message as below:
planetmy1:/var/spool/locks # rpm -Fvh http://server01/openssl-0.9.8a-18.26.x86_64.rpm
Retrieving http://server01/openssl-0.9.8a-18.26.x86_64.rpm
Preparing... Segmentation fault### ( 50%
In /var/log/messages, I can see similar error:
kernel: rpm[21904]: segfault at 0000000000bbbfb0 rip 00002b13dd4c51ba rsp 00007fffcd8c0150 error 4
The solution is:
[root@planetmy1 ~]# rpm --rebuilddb
use –rebuilddb to rebuild the database indices from the installed package headers.
Read more
Possibly Related Posts:
- How To Capture PUTTY Session Log
- How to Add Date And Time To Your Bash History on SuSE Linux
- Introduce Server Fault
- OpenVPN route issue
- How to clean EMC CX 3-80 Dirty Cache?
Introduce Server Fault
While I was checking out twitter, I found a new site Server Fault!
Server Fault is a collaboratively edited question and answer site for system administrators and IT professionals – regardless of platform. It’s 100% free, no registration required.
Note: Server Fault public beta will begin May 25th.
Server Fault is for system administrators and IT professionals, people who manage or maintain computers in a professional capacity. If you are in charge of …
* servers
* networks
* many desktop PCs (other than your own)… then you’re in the right place to ask your question! Well, as long as the question is about your servers, your networks, or desktops you support, anyway.
Possibly Related Posts:
- How To Capture PUTTY Session Log
- How to Add Date And Time To Your Bash History on SuSE Linux
- RPM Segmentation Fault
- OpenVPN route issue
- How to clean EMC CX 3-80 Dirty Cache?
OpenVPN route issue
OpenVPN is a full-featured open source SSL VPN solution that accommodates a wide range of configurations, including remote access, site-to-site VPNs, Wi-Fi security, and enterprise-scale remote access solutions with load balancing, failover, and fine-grained access-controls.
I wouldn’t repeat how I setup OpenVPN from scratch which you can found tons of useful guide on Google. Here, I would like to share my OpenVPN routing issue and solution.
Setup details as show below:
SERVER:
LAN = 172.16.7.25X/255.255.0.0
WAN = 219.95.19x.1xx/255.255.255.252
VPN = 172.31.0.x/255.255.0.0
[root@planetmy ~]# view /etc/openvpn/server.conf
port 1194
proto udp
dev tun
ca keys/ca.crt
cert keys/server.crt
key keys/server.key
dh keys/dh1024.pem
server 172.31.0.0 255.255.0.0
ifconfig-pool-persist ipp.txt
push “route 172.16.0.0 255.255.0.0″
keepalive 10 120
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 3
Read more
Possibly Related Posts:
- How To Capture PUTTY Session Log
- How to Add Date And Time To Your Bash History on SuSE Linux
- RPM Segmentation Fault
- Introduce Server Fault
- How to clean EMC CX 3-80 Dirty Cache?