06-22-2010
Maybe I have different firmware revisions, but that login routine doesn't look like an iLOM routine. Is there a terminal server involved?
10 More Discussions You Might Find Interesting
1. Solaris
Hello !
i'm facing an anoying problem during configuration of our new T5220 Enperise server. I've upgarded 'em with a pci-e ethernet expantion card for four additional networkinterfaces using the nxge drivers. i could fix them to 100 fdx rather simple by adding the following settings to the ... (6 Replies)
Discussion started by: moofoo
6 Replies
2. Solaris
Hi Peeps,
Apologies if this is the wrong forum for this, if it is can someone point me in the direction of the right one?
Problem:
I've dropped an XVR-300 Graphics card into a T5220, configured it to output and input from the screen and keyboard instead of the virtual console. It... (3 Replies)
Discussion started by: callmebob
3 Replies
3. Solaris
Hi,
I have Sun SPARC Enterprise T5140 and I can't access it via serial port using preconfigured administrator account, as described in Sun Integrated Lights Out Manager 2.0 User's Guide: I'm always receive "Login incorrect" message. I'm really confused! Does anyone experience such circumstances?... (12 Replies)
Discussion started by: Sapfeer
12 Replies
4. Solaris
I 've 2 different T5220 and both are showing different prompts when i ssh to the console.
1. Shows sc> ALOM
2. Shows -> ILOM
as far as i know the T5220 comes with ILOM , so why i 'm seeing 2 different type of console for same tyep of hardware ?
and i found that we... (6 Replies)
Discussion started by: fugitive
6 Replies
5. Solaris
Hi,
SC on one of my T5220 is not responding .. it does not show not let me type anything .. what could be the reason for it ? though when i powercycle the box from sc it shows me the system coming up but after that does not let me login thru sc
sc> console -f
Enter #. to return to ALOM. (2 Replies)
Discussion started by: fugitive
2 Replies
6. Solaris
We're just about to migrate a large application from an Enterprise 6900 to a pair of T5220s utilising LDOMs. Does anyone have any experience of LDOMs on this kit and can provide any recommendations or pitfalls to avoid?
I've heard that use of LDOMs can have an impact on I/O speeds as it's all... (9 Replies)
Discussion started by: JerryHone
9 Replies
7. Solaris
Hi,
We have two T5220 servers in our datacentre
one server is showing 64 processors online
and another showing 32 processors online
two are newly purchased, there is no hardware faults in this server
one server has 64gb memory and it shows 64 processors,
and other having 32gb memory and it... (5 Replies)
Discussion started by: rajasekg
5 Replies
8. Solaris
Hi Guys and Gals,
Wondering if anyone could help me, tricky one this.
Got a T5220 with a graphics card. When you power it on, it outputs its output to the screen and you can type commands with the keyboard etc.
But no matter what version of Solaris 10 you use, when you do a boot cdrom... (1 Reply)
Discussion started by: callmebob
1 Replies
9. Solaris
Hello guys,
can anyone give me some advice on how to perform
clean installation of Solaris 10 on T5220 ?
I am connected with serial management port on the machine,
i have the ok promt and now i should eject the dvdrom to insert
Solaris dvd into and start the clean install.
So how to do that... (3 Replies)
Discussion started by: tonijel
3 Replies
10. Solaris
Have a T5220 with Oracle SN stickers on outside with one SN, but the ILOM shows a different SN (from another server). It seems this is a issue with T5220's (a co-worker ran into similar problem with 2 of his servers, he just had the ILOM's swapped).
Anyone know the command to change the ILOM... (3 Replies)
Discussion started by: RTM
3 Replies
LEARN ABOUT OSF1
curs_initscr
curs_initscr(3) Library Functions Manual curs_initscr(3)
NAME
curs_initscr, initscr, newterm, endwin, isendwin, set_term, delscreen - Curses routines for screen initialization and manipulation
SYNOPSIS
#include <curses.h>
WINDOW *initscr(
void ); int endwin(
void ); int isendwin(
void ); SCREEN *newterm(
char *type,
FILE *outfd,
FILE *infd ); SCREEN *set_term(
SCREEN *new ); void delscreen(
SCREEN *sp );
LIBRARY
Curses Library (libcurses)
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
delscreen, initscr, endwin, isendwin, newterm, set_term: XCURSES4.2
Refer to the standards(5) reference page for more information about industry standards and associated tags.
DESCRIPTION
The initscr routine is almost always the first routine that applications call. (The exceptions are slk_init, filter, ripoffline, use_env
and, for multiple-terminal applications, newterm). The initscr routine determines the terminal type and initializes all Curses data struc-
tures. The routine also causes the first call to refresh to clear the screen. If errors occur, initscr writes an appropriate error message
to standard error and then exits; otherwise, the routine returns a pointer to stdscr. If the program needs an indication of error condi-
tions, newterm should be used instead of initscr; initscr should only be called once per application.
A program that outputs to more than one terminal should use the newterm routine for each terminal instead of initscr. A program that needs
an indication of error conditions, so it can continue to run in a line-oriented mode if the terminal cannot support a screen-oriented pro-
gram, would also use newterm. An application calls newterm once for each terminal. The routine returns a variable of type SCREEN * that
should be saved as a reference to that terminal. The routine's arguments are the type of the terminal to be used in place of $TERM, a file
pointer for output to the terminal, and another file pointer for input from the terminal. (If type is NULL, $TERM is used). Before exiting
Curses, the program must also call endwin for each terminal being used. If the program calls newterm more than once for the same terminal,
the first terminal referred to must be the last one for which endwin is called.
A program should always call endwin before exiting or escaping from Curses mode temporarily. This routine restores tty modes, moves the
cursor to the lower left-hand corner of the screen, and resets the terminal into the proper nonvisual mode. Calling refresh or doupdate
after a temporary escape causes the program to resume visual mode.
The isendwin routine returns TRUE if endwin has been called without any subsequent calls to wrefresh; otherwise, the routine returns FALSE.
The set_term routine switches between different terminals. The screen reference new becomes the new current terminal. The routine returns
the previous terminal. This is the only routine that manipulates SCREEN pointers; all other routines affect only the current terminal.
The delscreen routine frees storage associated with the SCREEN data structure. The endwin routine does not perform this operation, so
applications should call delscreen after endwin if a particular SCREEN is no longer needed. Applications must also close file pointers
passed to newterm.
NOTES
The header file <curses.h> automatically includes the header file <stdio.h>.
RETURN VALUES
The endwin routine returns the integer ERR upon failure and OK upon successful completion.
Routines that return pointers always return NULL on error.
SEE ALSO
Functions: curses(3), curs_kernel(3), curs_refresh(3), curs_slk(3), curs_util(3)
Others: standards(5)
curs_initscr(3)