SCO 5 and Getty


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers SCO 5 and Getty
# 1  
Old 02-02-2009
SCO 5 and Getty

Our medical practice has inherited an SCO 5 box with a practice management program, medical manager, installed on the box that we need to access on our Windows network. Boots fine and I can login with root no problem. Problem is, I can't get it to do anything because of these getty error messages. From what I can see, getty manages terminals, serial ones I guess. There are no serial devices connected to the server. I tried to comment out the references to getty in the inittab file but the error messages kept displaying while trying to edit the file using vi. I have 2 questions, (1) is there a way to kill the getty process all together so I can edit the file? and (2) do you know of any good programs that will serve terminal connections over TCP/IP?

Thanks,

Don
 
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ps aux|grep getty

what is the aim of this command: ps aux|grep getty (1 Reply)
Discussion started by: gfhgfnhhn
1 Replies

2. UNIX for Dummies Questions & Answers

getty

Can anyone give me a relatively simple definition of what a "getty" is? Are there multiple getty processes or types of getty processes? or is there just one? What does getty do in relation to a tty or pty? Thanks to all who respond. (1 Reply)
Discussion started by: google
1 Replies

3. UNIX for Dummies Questions & Answers

/usr/sbin/getty

How can i restart the console getty without rebooting the system on HPUX 11.0 Normally it will be stated by ps -ef | grep getty console 0:00 /usr/sbin/getty console console many thanx (4 Replies)
Discussion started by: iceman_denmark
4 Replies

4. UNIX for Advanced & Expert Users

Getty-problems in FreeBSD

Hi all, I'm having a disturbing problem with getty i fbsd (fbsd 4.5 on a compaq laptop). One day, when the boot process was complete, my logs were spammed with messages from getty: May 20 21:27:10 laptop getty: login_tty /dev/console: Operation not supported by device May 20 21:27:10 laptop... (1 Reply)
Discussion started by: kuba
1 Replies
Login or Register to Ask a Question
UBT(4)							   BSD Kernel Interfaces Manual 						    UBT(4)

NAME
ubt -- USB Bluetooth driver SYNOPSIS
ubt* at uhub? port ? configuration ? interface ? DESCRIPTION
The ubt driver provides support for USB Bluetooth dongles to the Bluetooth protocol stack. USB Bluetooth dongles provide two interfaces, both of which the ubt driver claims. The second interface is used for Isochronous data and will have several alternate configurations regarding bandwidth consumption, which can be set using the hw.ubtN.config sysctl(8) variable. The number of alternate configurations is indicated by the value in the hw.ubtN.alt_config variable, and the isoc frame size for the current configuration is shown in the hw.ubtN.sco_rxsize and hw.ubtN.sco_txsize variables. By default, configuration 0 is selected, which means that no bandwidth is used on the Isochronous interface and no SCO data can be sent. Consult the Bluetooth USB specification at https://www.bluetooth.org/ for complete instructions on setting bandwidth consumption. The fol- lowing extract may be useful as a general guidance though details may differ between manufacturers. 0 No active voice channels 1 One voice channel with 8-bit encoding 2 Two voice channels with 8-bit encoding, or one voice channel with 16-bit encoding. 3 Three voice channels with 8-bit encoding 4 Two voice channels with 16-bit encoding 5 Three voice channels with 16-bit encoding SEE ALSO
bluetooth(4), uhub(4), sysctl(8) HISTORY
This ubt device driver was originally a character device written by David Sainty and Lennart Augustsson. It was rewritten to support socket based Bluetooth access for NetBSD 4.0 by Iain Hibbert. CAVEATS
Isochronous data is seemingly not well supported over USB in the current system and to get SCO working, you may have to calculate the SCO packet size that the stack will use. This is the sco_mtu value reported by the btconfig(8) command, and when combined with the SCO header (3 bytes) should fit exactly into an integer number of Isochronous data frames where the frame size is indicated by the 'hw.ubtN.sco_txsize' sysctl variable. For example: I want one voice channel (which is all that is supported, for now) so am using configuration #2, with a frame length of 17 bytes. This gives possible values of: (17 * 1) - 3 = 14 (17 * 2) - 3 = 31 (17 * 3) - 3 = 48 (17 * 4) - 3 = 65 (17 * 5) - 3 = 82 etc. btconfig(8) shows the maximum SCO payload as 64 bytes, so I am using the next smaller size of 48, to minimize the overhead of the 3 header bytes. The SCO packet size can be changed using the 'scomtu' option to btconfig(8). The failure mode is that the USB Bluetooth dongle locks up though generally removal/reinsertion will clear the problem. BUGS
The Isochronous configuration can only be changed when the device is not marked up. BSD
August 27, 2006 BSD