Sponsored Content
Full Discussion: Solaris U10 - Crash OS
Operating Systems Solaris Solaris U10 - Crash OS Post 302841785 by Just Ice on Thursday 8th of August 2013 02:52:57 AM
Old 08-08-2013
so what is the reason to connect to the serial port if you already have console access with the monitor and the keyboard?

anyways, new solaris servers used to ship with silver-colored null modem adapters so you may see them around if you folks got the servers new ... if you do not see any of them and you cannot find a null modem, you can change the pinouts on a serial adapter to make your own null modem ... see the diagrams here for guidance on the pinouts ...
This User Gave Thanks to Just Ice For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris 8 crash on Enterprise 3500

Hi Should anyone be able to help, one of my colleagues was doing a truss this morning and I am not sure if it has offset the system crash, but we have had these type of errors coming up???? # ls ls: Cannot read /usr/lib/ld.so.1 Killed # ps -ef ps: Cannot read /usr/lib/ld.so.1 Killed #... (1 Reply)
Discussion started by: NAV4869
1 Replies

2. UNIX for Advanced & Expert Users

Solaris Server Crash

We have had a server (Solaris 2.6) hardisk crash. When booting the server we get: ok> boot -S Boot Device: /sbus/espdmc@e, 8400000/esp@e,8800000/sd@0,0 short read 0x2000 chars read disk read error The only way we can get into the console is to ok> boot cdrom whereby everything (e.g.... (3 Replies)
Discussion started by: Breen
3 Replies

3. Solaris

problem with tar command in solaris9 on sun U10

I try to install globus toolkit 4 and have major problem that's error in tar command while it install by make command tar -C /usr/local/globus/ -xzf binary-trees/globus_libtool-*/*.tar.gz tar: C: unknown function modifierand it notice me to use tar {c|r|t|u|x} I think it can't use -z... (3 Replies)
Discussion started by: Harmut
3 Replies

4. Solaris

Sparc Solaris 8 crash dump

My sparc solaris 8 server crashed/rebooted yesterday and I have the vmcore files. I have some initial output from SCAT and ACT. I have not included all but any info would be helpful. I can supply more output if necessary. Thanks you. Can I have any information about this ACT and SCAT... (2 Replies)
Discussion started by: csgonan
2 Replies

5. Solaris

Solaris 10 zone crash dump file?

Hi, I'm running Solaris 10 with a zone called "testzone" If I do a "reboot -d" on the host, as expected the kernet panics, reboots and creates a crash dump file in /var/crash However no crash file is created in testzone. My question is how can I tell if a zone crashs or shuts down... (4 Replies)
Discussion started by: fastexit
4 Replies

6. Solaris

Question with Solaris Crash Analysis Tool with Solaris 9

Hello all. I am new hear and would like to ask a question regarding to the Solaris Crash Analysis Tool. We are analyzing the results of "thread summary" but not quite sure what the asterisk represents. Following are the items that asterisk were attached. 50* threads sleeping on a semaphore (49... (1 Reply)
Discussion started by: YuW
1 Replies

7. Solaris

Can't Log into Solaris 10 u10 due to Pam and DH errors

Dears,, i hope everything is going fine with you,, Yesterday i was trying to log into My Solaris 10 u10 x86 Via SSH , But it showing me many error message and refusing to login even with with the root account and below you can find the error message: # ssh -v root@192.168.10.1... (6 Replies)
Discussion started by: ieee99
6 Replies

8. Solaris

Check for existence of crash on Solaris 10

Hey all what is the command to check "Check for existence of crash/coredump files in /var/crash/"hostname" directory" thanks for help (4 Replies)
Discussion started by: gema.utama
4 Replies

9. Solaris

How to recover x86 Solaris 10 u10 boot record/grub menu overwritten by Debian 9?

I installed x86 Solaris 10 update 10 after Windows XP, later I removed xp and installed Debian 9 stretch on the same partition but, Debian couldn't find any other os so it deleted Solaris 10 grub or did something like that I couldn't got. I thought I would be able to recover the lost record by... (0 Replies)
Discussion started by: vectrum
0 Replies
ports(7)						 Miscellaneous Information Manual						  ports(7)

NAME
ports, port_names - Device (tty and lp) names for serial and parallel ports SYNOPSIS
Default Serial Ports: /dev/tty00 /dev/tty01 (not present on a single-port system) Parallel Port: /dev/lp0 DESCRIPTION
AlphaStation and AlphaServer systems provide one or two 9-pin serial communication ports. These ports are usually labelled 1 (COMM1) and 2 (COMM2), but they may be identified by different icons. Using the appropriate serial cable and terminator, you can connect a serial printer, external modem, or character-cell terminal to a serial port. Most AlphaStation and AlphaServer systems also provide one parallel port, for use with a parallel printer. When you add a device to your system, the installation documentation may instruct you to map the device pathname to the port. These devices are located in the /dev directory. For serial-line ports, the two default device pathnames are: This pathname always maps to 1, COMM1, the lowest port number, an icon for a terminal console, or the only serial port (on a single-port system). This pathname always maps to 2, COMM2, the next numbered port, or (if one serial port is labeled with an icon for a terminal console) the remaining serial port. If your system hardware has been extended to include additional serial ports, the pathnames /dev/tty02, /dev/tty03, and so forth, may also be available to you. However, most systems have only /dev/tty00 and /dev/tty01 as the device pathnames for serial ports. The one parallel port on an AlphaStation or AlphaServer may be labeled with the word printer or a printer icon. On some systems, the paral- lel port may not be labeled. The device pathname for the parallel port is /dev/lp0. Currently, Tru64 UNIX does not fully support parallel printers, so fewer devices are connected to this port as compared to serial ports. If you are connecting a terminal console to your system, it must be connected to the serial port mapped to /dev/tty00. For other serial devices, it does not matter which of the serial ports you choose for the connection. For example, suppose you are setting up a system that has two serial ports, labeled 1 and 2. You intend to use a serial-line terminal rather than a workstation monitor as the system console and also want to connect a serial-line printer to the system. In this case, you must connect the terminal to the port labeled 1 (with the device pathname /dev/tty00). Therefore, you must connect the printer to the remaining port labeled 2 (with the device pathname /dev/tty01). If, for the same type of system, you intend to use a workstation monitor as the system console, it does not matter which serial port you use for a serial-line printer or modem. In other words, you can connect the printer to either port 1 (with pathname /dev/tty00) or port 2 (with pathname /dev/tty01). When prompted to enter a /dev/tty** pathname by the lprsetup script or the Print configuration tool in the CDE Application Manager, you would specify /dev/tty00 if you connected the printer to port 1 or /dev/tty01 if you connected the printer to port 2. See the System Administration manual for more information on setting up consoles (including remote consoles) and printers. See the modem(7) reference page for more information on setting up modems. SEE ALSO
Commands: lprsetup(8) Devices: ace(7), modem(7) System Administration delim off ports(7)
All times are GMT -4. The time now is 09:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy