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
CFREE(3)						     Linux Programmer's Manual							  CFREE(3)

NAME
cfree - free allocated memory SYNOPSIS
#include <stdlib.h> /* In SunOS 4 */ int cfree(void *ptr); /* In glibc or FreeBSD libcompat */ void cfree(void *ptr); /* In SCO OpenServer */ void cfree(char *ptr, unsigned num, unsigned size); /* In Solaris watchmalloc.so.1 */ void cfree(void *ptr, size_t nelem, size_t elsize); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): cfree(): _BSD_SOURCE || _SVID_SOURCE DESCRIPTION
This function should never be used. Use free(3) instead. 1-arg cfree In glibc, the function cfree() is a synonym for free(3), "added for compatibility with SunOS". Other systems have other functions with this name. The declaration is sometimes in <stdlib.h> and sometimes in <malloc.h>. 3-arg cfree Some SCO and Solaris versions have malloc libraries with a 3-argument cfree(), apparently as an analog to calloc(3). If you need it while porting something, add #define cfree(p, n, s) free((p)) to your file. A frequently asked question is "Can I use free(3) to free memory allocated with calloc(3), or do I need cfree()?" Answer: use free(3). An SCO manual writes: "The cfree routine is provided for compliance to the iBCSe2 standard and simply calls free. The num and size argu- ments to cfree are not used." RETURN VALUE
The SunOS version of cfree() (which is a synonym for free(3)) returns 1 on success and 0 on failure. In case of error, errno is set to EINVAL: the value of ptr was not a pointer to a block previously allocated by one of the routines in the malloc(3) family. CONFORMING TO
The 3-argument version of cfree() as used by SCO conforms to the iBCSe2 standard: Intel386 Binary Compatibility Specification, Edition 2. SEE ALSO
malloc(3) COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. 2007-07-26 CFREE(3)