SCO UNIX error 6, HELP


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers SCO UNIX error 6, HELP
# 1  
Old 02-01-2002
Data SCO UNIX error 6, HELP

I have a system here running "SCO UNIX System V/386, Release 3.2" I'm not sure if someone has changed anything, but all of the sudden I get constant scrolling errors...

"*** /etc/getty ttyr006 m (CURRENT TIME/DATE):
Cannot open line ttyr006: No such device or address (error 6)"

this scrolls from ttyr000-ttyr007.

The machine seems to be operating fine otherwise, but when clients connect to it via telnet, it is MUCH slower then ever before... Can anyone help me figure out this error and how to get it to stop


N/M I think I figured out the problem, there was a device attached to accomodate some serial connections and it was disconnected, so I reconnected it and it seems fine now.

Last edited by PBNOSGT; 02-01-2002 at 04:45 PM..
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Error UNIX: UNIX SCO release 5.05 system does not boot

UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies

2. SCO

Getting error sco unix 507 from cdrom:no controller for device you chosen

Installing SCO UNIX 507 on Dell Poweredge T610. It has no floppy so I downloaded the BTLD onto CD from SCO site to load without floppy drive. BTLD loads ok. when i get to the Media to be used, no matter what option i chose i get the error: No controller for device you have chosen. During bootup you... (9 Replies)
Discussion started by: romanglad112
9 Replies

3. SCO

Sco Unix HFS file system error

HI, I have sco unix server currently i am trying to boot its not booting and giving error as HTFS error message contains - Warning : can not identify block 496 for i number 438 on HTFS dev hd (1/42). Warning : exit - /etc/init (PID 1) died, status 0x0000008B server is not getting boot... (0 Replies)
Discussion started by: islamsk
0 Replies

4. SCO

load sco xenix and sco unix binary ?

Hi I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7. I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Discussion started by: javad1_maroofi
0 Replies

5. UNIX for Dummies Questions & Answers

unix system v release 3.2 (sco-unix?)

another unix printing issue. our client based pc's used to print some form's to our hp printer. as of the moment they can not print. i have checked & did the ff: #lpstat -r (scheduler is running) i dunno if i need to restart the whole unix box via shutdown or just checking at... (15 Replies)
Discussion started by: jedimaster
15 Replies

6. UNIX for Dummies Questions & Answers

SCO UNIX "TCP/IP not licensed error"

I have been running 5.0.02 for more than 10 years in its present configuration. I am running a business software package on it (text based). I am trying to use my windows machines to access it through a program like "reflections" so that I can run my software from different systems but I get... (2 Replies)
Discussion started by: Parkegio
2 Replies

7. Filesystems, Disks and Memory

Unix Sco Open Server, Windows Computers Problem Access Unix Shared Files Help!!!!!

Hello Moto I hope someone can help We's here at work, have a unix box with sco openserver 5 on it, so it has a nice gui interface.. and also a fair few windows computers.. a system admin guy b4 me, has set up a user called neil, which can, when u try to access the unix box using windows... (2 Replies)
Discussion started by: haggo
2 Replies

8. UNIX for Advanced & Expert Users

Error during Sco Unix boot

Hi friends, i am getting the following error while booting my system which has SCo UNIX . ========================= H iinit PANIC: srmountfun-Error 22 mounting of rootdev hd(1/42) cannot dump 40863 pages to dempdev hd(1/41) : Space for only 0 pages. Dump not completed. safe to power off... (3 Replies)
Discussion started by: sveera
3 Replies

9. UNIX for Advanced & Expert Users

FTP - Sco Unix to ProFTPD Error

First off I did try google for help on this topic, didn't really find anything. When I try to ftp from my SCO Unix box (SCO_SV servername 3.2 5.0.5 i386) to a proFTPD server within my company I get this error Connected to 10.?.?.?. 220 ProFTPD Server ftp.hostname.com Name (10.?.?.?:root):... (1 Reply)
Discussion started by: whegra
1 Replies

10. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine... (0 Replies)
Discussion started by: Cerberus
0 Replies
Login or Register to Ask a Question
uname(1)							   User Commands							  uname(1)

NAME
uname - print name of current system SYNOPSIS
uname [-aimnprsvX] uname [-S system_name] DESCRIPTION
The uname utility prints information about the current system on the standard output. When options are specified, symbols representing one or more system characteristics will be written to the standard output. If no options are specified, uname prints the current operating sys- tem's name. The options print selected information returned by uname(2), sysinfo(2), or both. OPTIONS
The following options are supported: -a Prints basic information currently available from the system. -i Prints the name of the platform. -m Prints the machine hardware name (class). Use of this option is discouraged. Use uname -p instead. See NOTES section below. -n Prints the nodename (the nodename is the name by which the system is known to a communications network). -p Prints the current host's ISA or processor type. -r Prints the operating system release level. -s Prints the name of the operating system. This is the default. -S system_name The nodename may be changed by specifying a system name argument. The system name argument is restricted to SYS_NMLN characters. SYS_NMLN is an implementation specific value defined in <sys/utsname.h>. Only the super-user is allowed this capability. This change does not persist across reboots of the system. Use sys-unconfig(1M) to change a host's name per- manently. -v Prints the operating system version. -X Prints expanded system information, one information element per line, as expected by SCO UNIX. The displayed information includes: o system name, node, release, version, machine, and number of CPUs. o BusType, Serial, and Users (set to "unknown" in Solaris) o OEM# and Origin# (set to 0 and 1, respectively) EXAMPLES
Example 1 Printing the OS name and release level The following command: example% uname -sr prints the operating system name and release level, separated by one SPACE character. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of uname: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. SYSV3 This variable is used to override the default behavior of uname. This is necessary to make it possible for some INTERACTIVE UNIX Systems and SCO UNIX programs and scripts to work properly. Many scripts use uname to determine the SYSV3 type or the version of the OS to ensure software is compatible with that OS. Setting SYSV3 to an empty string will make uname print the following default values: nodename nodename 3.2 2 i386 The individual elements that uname displays can also be modified by setting SYSV3 in the following format: os,sysname,node,rel,ver,mach os Operating system (IUS or SCO). sysname System name. node Nodename as displayed by the -n option. rel Release level as displayed by the -r option. ver Version number as displayed by the -v option. mach Machine name as displayed by -m option. Do not put spaces between the elements. If an element is omitted, the current system value will be used. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
arch(1), isalist(1), sys-unconfig(1M), sysinfo(2), uname(2), nodename(4), attributes(5), environ(5), standards(5) NOTES
Independent software vendors (ISVs) and others who need to determine detailed characteristics of the platform on which their software is either being installed or executed should use the uname command. To determine the operating system name and release level, use uname -sr. To determine only the operating system release level, use uname -r. Notice that operating system release levels are not guaranteed to be in x.y format (such as 5.3, 5.4, 5.5, and so forth); future releases could be in the x.y.z format (such as 5.3.1, 5.3.2, 5.4.1, and so forth). In SunOS 4.x releases, the arch(1) command was often used to obtain information similar to that obtained by using the uname command. The arch(1) command output "sun4" was often incorrectly interpreted to signify a SunOS SPARC system. If hardware platform information is desired, use uname -sp. The arch -k and uname -m commands return equivalent values; however, the use of either of these commands by third party programs is dis- couraged, as is the use of the arch command in general. To determine the machine's Instruction Set Architecture (ISA or processor type), use uname with the -p option. SunOS 5.11 17 Sep 2003 uname(1)