Sponsored Content
Operating Systems SCO Watchdog Problem In Unix Server Post 69206 by RTM on Wednesday 13th of April 2005 08:28:35 AM
Old 04-13-2005
As far as edblock table error, read the answer towards the bottom of the link - you may not have enough physical memory to run the amount of connections or not enough memory allocated for the amount of connections. More than likely your watchdog errors are either from this problem or you may have some bad memory.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UNIX server problem

We have a site on our UNIX server which includes downloadable word and excel files. The word files are downloading files, and the excel files are trying to display in the browser instead of downloading properly. We have determined that this is not a browser issue....there is something that needs to... (1 Reply)
Discussion started by: rlwd
1 Replies

2. UNIX for Dummies Questions & Answers

Unix Open Server 5.0.2 Instalation Problem

hi, I am unable to install unix open server 5.0.2 on desktop P-III,750 MHz,20GB HDD (IDE) 1.44 MB FDD, ATAPI IDE 48X cd rom. I prepared 5 boot floppies i.e. boot(N00), AHSBTLD(01), IPXSPX(01),NUC(01), NUC(02). The system was booted with boot(N00) floppy. After booting it asked to identify... (3 Replies)
Discussion started by: Manjit
3 Replies

3. Shell Programming and Scripting

IInd Hard Disk Mounting Problem on 1st HDD On SCO UNIX Open Server

Hi Engg. ! :mad: I have a harddisk on which SCO UNIX Open Server was installed. There was some data (in .dbf format) on it. Present condition of HDD is that it is not booting. Now I want to mount this HDD through other HDD on which SCO UNIX Open Server is installed by attaching... (0 Replies)
Discussion started by: Niraj Gopal Sha
0 Replies

4. 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

5. UNIX for Dummies Questions & Answers

FTP problem on unix-server

hi there, i am a sap-programmer and i sent pdf-files via FTP from sap (on an iseries-machine) to a UNIX-server every day. i am doing it via MPUT *.pdf It works well until today. I got the ftp-message "Arguments too long"....i searched for it in the internet and here in the forum. it says... (9 Replies)
Discussion started by: smartin999
9 Replies

6. UNIX for Dummies Questions & Answers

A bit of a problem with a UNIX based server.

Alright. As the title states, I'm working with a UNIX based web server(Sun Fire v120). The problem I'm currently having is trying to properly configure it for hosting. If anyone could help me out, it would be great. Much thanks. -XTIZ3 (2 Replies)
Discussion started by: XTIZ3
2 Replies

7. UNIX and Linux Applications

Problem with accessing subversion installed on unix server through windows GUI

We are using subversion as a version control system in our project. We are connecting to client`s sun Solaris box through check point VPN. Client has installed subversion . We have created repository and add files to it. Now we want to access the same from our windows machine (through... (0 Replies)
Discussion started by: aasid
0 Replies

8. Shell Programming and Scripting

Problem while Transferring files to UNIX server

Hi When I m transferring my file to UNIX server using filezilla , after every line in a file ^M is shown. Because of this ^M I cannot execute my file/scripts Why so ??? Any suggestions... (7 Replies)
Discussion started by: dashing201
7 Replies

9. UNIX for Advanced & Expert Users

Space Problem in Unix Server

Hi, I am having space issues in unix server. The free space is getting reduced gradually in my server. I gave the df -g /folder1 command to check the free space and it showed as 0.75 GB. I then deleted some files from the unix server and then checked the size of each dir using the du... (5 Replies)
Discussion started by: mick_000
5 Replies

10. Programming

Problem with Perl script after moving from a Windows/Apache Server to a UNIX server.

I have a Perl script that worked fine before moving it to justhost.com. It was on a Windows/Apache server. Just host is using UNIX. Other Perl scripts on other sites that were also moved work fine so I know Perl is functioning. The script is called cwrmail.pl and is located in my cgi-bin. When I... (9 Replies)
Discussion started by: BigBobbyB
9 Replies
PTY(7)							     Linux Programmer's Manual							    PTY(7)

NAME
pty - pseudo-terminal interfaces DESCRIPTION
A pseudo-terminal is a pair of virtual character devices that provide a bidirectional communication channel. One end of the channel is called the master; the other end is called the slave. The slave end of the pseudo-terminal provides an interface that behaves exactly like a classical terminal. A process that expects to be connected to a terminal, can open the slave end of a pseudo-terminal and then be driven by a program that has opened the master end. Anything that is written on the master end is provided to the process on the slave end as though it was input typed on a terminal. For example, writing the interrupt character (usually control-C) to the master device would cause an interrupt signal (SIGINT) to be generated for the foreground process group that is connected to the slave. Conversely, anything that is written to the slave end of the pseudo-terminal can be read by the process that is connected to the master end. Pseudo-terminals are used by applications such as network login services (ssh(1), rlogin(1), telnet(1)), terminal emulators, script(1), screen(1), and expect(1). Historically, two pseudo-terminal APIs have evolved: BSD and System V. SUSv1 standardized a pseudo-terminal API based on the System V API, and this API should be employed in all new programs that use pseudo-terminals. Linux provides both BSD-style and (standardized) System V-style pseudo-terminals. System V-style terminals are commonly called Unix 98 pseudo-terminals on Linux systems. Since kernel 2.6.4, BSD-style pseudo-terminals are considered deprecated (they can be disabled when configuring the kernel); Unix 98 pseudo-terminals should be used in new applications. Unix 98 pseudo-terminals An unused Unix 98 pseudo-terminal master is opened by calling posix_openpt(3). (This function opens the master clone device, /dev/ptmx; see pts(4).) After performing any program-specific initializations, changing the ownership and permissions of the slave device using grantpt(3), and unlocking the slave using unlockpt(3)), the corresponding slave device can be opened by passing the name returned by ptsname(3) in a call to open(2). The Linux kernel imposes a limit on the number of available Unix 98 pseudo-terminals. In kernels up to and including 2.6.3, this limit is configured at kernel compilation time (CONFIG_UNIX98_PTYS), and the permitted number of pseudo-terminals can be up to 2048, with a default setting of 256. Since kernel 2.6.4, the limit is dynamically adjustable via /proc/sys/kernel/pty/max, and a corresponding file, /proc/sys/kernel/pty/nr, indicates how many pseudo-terminals are currently in use. For further details on these two files, see proc(5). BSD pseudo-terminals BSD-style pseudo-terminals are provided as precreated pairs, with names of the form /dev/ptyXY (master) and /dev/ttyXY (slave), where X is a letter from the 16-character set [p-za-e], and Y is a letter from the 16-character set [0-9a-f]. (The precise range of letters in these two sets varies across Unix implementations.) For example, /dev/ptyp1 and /dev/ttyp1 constitute a BSD pseudo-terminal pair. A process finds an unused pseudo-terminal pair by trying to open(2) each pseudo-terminal master until an open succeeds. The corresponding pseudo- terminal slave (substitute "tty" for "pty" in the name of the master) can then be opened. FILES
/dev/ptmx (Unix 98 master clone device) /dev/pts/* (Unix 98 slave devices) /dev/pty[p-za-e][0-9a-f] (BSD master devices) /dev/tty[p-za-e][0-9a-f] (BSD slave devices) NOTES
A description of the TIOCPKT ioctl(2), which controls packet mode operation, can be found in tty_ioctl(4). The BSD ioctl(2) operations TIOCSTOP, TIOCSTART, TIOCUCNTL, and TIOCREMOTE have not been implemented under Linux. SEE ALSO
select(2), setsid(2), forkpty(3), openpty(3), termios(3), pts(4), tty(4), tty_ioctl(4) COLOPHON
This page is part of release 3.25 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/. Linux 2005-10-10 PTY(7)
All times are GMT -4. The time now is 05:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy