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
invcutter(1)						      General Commands Manual						      invcutter(1)

Name
       invcutter - generate subset inventory files

Syntax
       /usr/sys/dist/invcutter [ -d ] [ -f root-path ] [ -f version-code ]

Description
       The  command  reads master inventory records from standard input.  A subset inventory record is written to standard output for every record
       read from the input. The information contained in the output record is derived from the input record and the file attribute information	in
       the file hierarchy rooted in the current directory.

Options
       -d		   Enable debugging. No useful diagnostics are printed.

       -f root-path	   Specify an alternate root path for finding file attribute information.

       -v version-code	   Specify a 3-digit version code for use in the version field of the output records. The default version code is 010.

Restrictions
       All input records must be sorted in ascending order on the pathname field.

       Files described in an input record which exist as sockets in the file hierarchy are not processable.

       If a file is described in an input record has a link count greater than 1, all other links to the file must be represented in the input.

Examples
       The following command will generate inventory records for the master inventory entries in PDS020.mi containing version fields set to 020:
	   invcutter -v 020 < PDS020.mi

Return Values
       An exit status of 0 is returned if all goes well. An exit status of 1 is returned if an error occurs. See Diagnostics.

Diagnostics
       "cannot chdir to pathname (error-message)"
       The  program  cannot  change  directories to the pathname directory specified with the -f option. The error-message will provide additional
       information.

       "sort error, record #n"
       The nth input record is not in the correct sort order. All input records must be in ascending  ASCII  colating  sequence  on  the  pathname
       field.

       "cannot stat filename (error-message)"
       An error has occurred attempting to read the attributes of filename.  The error-message explains exactly what happened.

       "pathname: illegal file type code 0140000"
       The file pathname is a socket. Sockets are not supported as valid file types for distribution.

       "unresolved nlink n: pathname"
       This indicates that file pathname in the master inventory is linked to n files which do not appear in the master inventory. Check inventory
       for validity with the program.

       "n unresolved hard links"
       This is an informational message stating how many files were detected in the input inventory which had unresolved links.

See Also
       newinv(1), stl_inv(5), stl_mi(5)
       Guide to Preparing Software for Distribution on ULTRIX Systems

																      invcutter(1)