Screen Useful links :
http://www.catonmat.net/download/screen.cheat.sheet.pdf
http://neophob.com/2007/04/gnu-screen-cheat-sheet/
Rough draft :
--------------
In putty screen mode, usually we can not scroll back using scroll bars to see the past output logs.
There may be ways to achieve this. But, I don't know.
For example, I am having a following screen output, with 2 sessions.
-------------------SCREEN SHOT---------------------------------
bash-2.05b$
Server1 0* ksh 1- ksh
--------------------------------------------------------------
In Screen 0, let me execute a command which emits lot of output. (For example, 'man ls' command)
I set the editor mode as 'vi'.
If I want to scroll back in this screen, I will go to Screen Escape mode (Ctrl + a).
[Though I set the Screen Escape mode sequence as (Ctrl + z)]
Then using vi navigation key board commands (like pressing 'k' to move up the cursor, Ctrl + B to move backwards.) go to the desired position to place your cursor.
1.) Press space bar to start your selection.
2.) Navigate through the screen to select the items using 'vi' editor navigation keys. It is a standard vi command to select from the current cursor position to end of the file. One best option is, pressing 'G' [shift + g] to go to the bottom of the screen.
Some times, there may not be enough screen buffer available. Need to find a way how to increase this buffer space.
-------------------------------SCREEN SHOT-------------------------------------------------------
bash-2.05b$ man ls
ls(1) ls(1)
NAME
ls, lc, l, ll, lsf, lsr, lsx - list contents of directories
SYNOPSIS
ls [-abcdefgilmnopqrstuxACFHLR1] [names]
lc [-abcdefgilmnopqrstuxACFHLR1] [names]
l [ls_options] [names]
ll [ls_options] [names]
lsf [ls_options] [names]
lsr [ls_options] [names]
lsx [ls_options] [names]
DESCRIPTION
For each directory argument, the ls command lists the contents of the
directory. For each file argument, ls repeats its name and any other
information requested. The output is sorted in ascending collation
order by default (see Environment Variables below). When no argument
is given, the current directory is listed. When several arguments are
given, the arguments are first sorted appropriately, but file
arguments appear before directories and their contents.
If you are a user with appropriate privileges, all files except . and
.. are listed by default.
There are three major listing formats. The format chosen depends on
whether the output is going to a login device (determined by whether
output device file is a tty device), and can also be controlled by
option flags.
The default format for a login device is to list the contents of
directories in multicolumn format, with entries sorted vertically by
column. (When individual file names (as opposed to directory names)
appear in the argument list, those file names are always sorted across
the page rather than down the page in columns because individual file
names can be arbitrarily long.) If the standard output is not a login
Server1 0* ksh 1- ksh
----------------------------------------------------------------------
3.) Press space bar again to complete the selection / copy process.
-------------------------------------SCREEN SHOT-------------------------------------------
specified on the command line, ls evaluates the file
information and file type to be those of the file referenced
by the link, and not the link itself. However, ls writes the
name of the link itself and not the file referenced by the
link.
-L Evaluate the file information and file type for all symbolic
links (whether named on the command line or encountered in a
file hierarchy) to be those of the file referenced by the
link, and not the link itself. However, ls writes the name
of the link itself and not the file referenced by the link.
When -L is used with -l, write the contents of symbolic
links in the long format.
-R Recursively list subdirectories encountered.
-1 (one) List the file names in single column format regardless
of the output device. This forces single column format to
the user's terminal.
Specifying more than one of the options in the following mutually
exclusive pairs is not considered an error: -C and -l (ell), -m and -l
(ell), -x and -l (ell), -C and -1 (one), -H and -L, and -c and -u.
ls is known by several shorthand-version names for the various
formats:
l is equivalent to ls -m
ll is equivalent to ls -l (ell)
lsf is equivalent to ls -F
lsr is equivalent to ls -R
lsx is equivalent to ls -x
bash-2.05b$
Copied 7568 characters into buffer
-----------------------------------------------------------------------------------------------------------
4.) Open your file in vi editor, and get into insert mode by pressing 'i'.
5.) Go to Screen paste mode by pressing, 'Ctrl + a' and ']' keys.
Voila ! All your selected contents are pasted into the file.
Save the file by 'Esc + :wq'.
Showing posts with label hp ux. Show all posts
Showing posts with label hp ux. Show all posts
Wednesday, December 12, 2012
Monday, July 2, 2012
HP UX - Mounting NFS filesystem simple example
Mounting the NFS filesystem: Simple Example : (Reference)
Let me mount the '/usr/sarav' directory located in the remote SERVER machine to the local CLIENT machine in '/var/sarav_mounted' directory.
In Server,
1.) Add the filesystem to be mounted in /etc/exports file.
SERVER# cat /etc/exports
/usr/sarav
SERVER#
2.) Export the filesystem.
SERVER# exportfs -a
SERVER# exportfs
/usr/sarav
SERVER# cd /usr/sarav
SERVER# ls -ltr
total 32
drwxrwxrwx 3 root sys 96 Apr 25 21:13 Modules
drwxrwxrwx 2 root sys 8192 Apr 25 21:24 MyPrograms
drwxrwxrwx 2 root sys 8192 Jun 6 16:46 Scripts
SERVER# showmount -e
export list for SERVER:
/usr/sarav (everyone)
SERVER#
In Client,
1.) Create a directory which will be used to mount to the server side directory and mount it.
CLIENT# mkdir /var/sarav_mounted
CLIENT# mount -F nfs SERVER:/usr/sarav /var/sarav_mounted
CLIENT# mount
/var/sarav_mounted on SERVER:/usr/sarav rsize=32768,wsize=32768,NFSv3,dev=2 on Mon Jul 2 16:14:20 2012
2.) Now access the remotely located filesystem by the mounted filesystem name as if you are accessing the local filesystem.
CLIENT# cd /var/sarav_mounted
CLIENT# ls -ltr
total 32
drwxrwxrwx 3 root sys 96 Apr 25 21:13 Modules
drwxrwxrwx 2 root sys 8192 Apr 25 21:24 MyPrograms
drwxrwxrwx 2 root sys 8192 Jun 6 16:46 Scripts
CLIENT#
Thursday, June 14, 2012
All SCTP RFCs Chart
All the up-to-date RFCs can be found at : http://www.rfc-editor.org/rfc-index2.html
Here, I have listed only the current SCTP RFCs and their inter-dependencies (As on June 14, 2012).
As the name implies, INFORMATIONAL RFCs are better than the PROPOSED STANDARD RFCs to understand the protocol !
RFC 4960 is the latest SCTP PROPOSED STANDARD RFC.
Definitions :
--------------
RFC = Request For Comments
SCTP = Stream Control Transmission Protocol
...........> Extended by RFC
--------> Obsoleted by RFC
'PROPOSED STANDARD' RFCs CHART
````````````````````````````````````````````````````
---+---- June 14, 2012
|
| .....> 6526 (IP Flow Information Export (IPFIX) Per SCTP Stream - Mar 2012)
| .
| .
| .....> 6525 (SCTP Stream Reconfiguration - Feb 2012)
| .
| .
| .....> 6096 (SCTP chunk flags registration - Jan 2011)
| .
| .
| .....> 6083 (Datagram Transport Layer Security (DTLS) for SCTP)
| .
| .....> 5811 (SCTP-Based Transport Mapping Layer (TML) for Forwarding
| . and Control Element Separation (ForCES) Protocol - Mar 2010)
| .
| .
| .....> 5043 (SCTP Direct Data Placement (DDP) Adaptation - Oct 2007)
| .
| .
| .....> 5061 (SCTP Dynamic Address Reconfiguration - Sep 2007)
| .
| .
4960 (SCTP - Sep 2007)
^
|
| .....> 4895 (Authenticated Chunks for the SCTP - Aug 2007)
| .
| .
| .....> 4820 (Padding Chunk and Parameter for the SCTP - Mar 2007)
| .
| .
| .....> 4168 (SCTP as Transport for Session Initiation Protocol (SIP)
| .
| .....> 3873 (SCTP Management Information Base (MIB) - Sep 2004)
| .
| .
| .....> 3758 (SCTP Partial Reliability Extension - May 2004)
| .
| .
| .....> 3554 (On the Use of SCTP with IPsec - July 2003)
| .
| .
2960 (SCTP - Oct 2000)
[Note : RFC 3309 (SCTP Checksum change - Sep 2002) updates RFC 2960, is not showed in the above chart as it is Obsoleted by RFC 4960. ]
INFORMATIONAL RFCs
```````````````````
6458 (Sockets API Extensions for the SCTP - Dec 2011)
5062 (Security Attacks Found Against SCTP and Current Countermeasures - Sep 2007)
4460 (SCTP Specification Errata and Issues - Apr 2006)
4166 (Telephony Signalling Transport over SCTP Applicability Statement - Feb 2006)
3286 (An Introduction to the SCTP) - May 2002)
EXPERIMENTAL RFCs
``````````````````
6084 (General Internet Signaling Transport (GIST) over SCTP and Datagram Transport Layer Security (DTLS) - Jan 2011)
5827 (Early Retransmit for TCP and SCTP - May 2010)
4138 (Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the SCTP - Aug 2005)
3708 (Using TCP Duplicate Selective Acknowledgement (DSACKs) and SCTP Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions - Feb 2004)
BEST CURRENT PRACTICE
``````````````````````
6335 Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry - Aug 2011
Subscribe to:
Posts (Atom)